What should a DC-Baltimore founder evaluate before hiring startup counsel?

Evaluate fit against the legal operating pattern your company actually runs on, not whether the attorney says they work with startups. Six criteria do most of the work: stage-specific experience you can verify (entity formation, SAFE or note rounds, priced financings the attorney personally handled or supervised), engagement-letter clarity on in-scope versus out-of-scope work and fee structure, tested responsiveness, referrals and track record you sourced independently, the boutique-versus-national trade-off for your stage, and region-specific sector knowledge. Then confirm jurisdictional coverage across Maryland, DC, and Virginia matches your footprint. The founder interview checklist in this article turns each of these into a specific question to ask.

How can I tell real startup experience from a general corporate attorney who says they work with startups?

Ask specifically for representative experience with entity formations, SAFE or convertible note rounds, and priced equity financings, and ask whether the attorney personally handled that work or supervised it directly, rather than pointing to the firm's general experience. Where the attorney can do so consistent with client consent and confidentiality obligations, ask about references, testimonials, or public representative matters. If the attorney lists startups as one of several practice areas rather than a core client category, that is worth noting, not disqualifying, but it changes what you should expect on responsiveness and pattern recognition.

Can one attorney handle Maryland, DC, and Virginia startup legal issues?

Not automatically, because there is no reciprocity across the three. An attorney admitted in Maryland and DC can handle Maryland and DC state-specific work and can advise on federal matters such as IP, securities, and employment regardless of where your entity sits. Virginia-specific matters, meaning Virginia employees, Virginia operations, or a Virginia entity, generally require Virginia admission or coordination with Virginia-licensed counsel. The selection point is not finding one person licensed everywhere. It is confirming that counsel's coverage, plus a stated plan for coordinating out-of-jurisdiction matters, matches where your company actually operates.

Does a Maryland or DC startup actually need local counsel?

State-specific formation and governance work generally calls for counsel admitted in that state, or coordinating with someone who is, because Maryland and DC each have their own corporate statutes and bar rules. Federal matters such as IP, securities, and employment can be handled by counsel admitted in either jurisdiction. So the real question is whether a given attorney's jurisdictional coverage lines up with your footprint, not whether every task strictly requires a local license. Confirm coverage before you rely on the advice rather than after a jurisdiction-specific issue surfaces.

What should be included in an outside general counsel engagement for a startup, and what falls outside it?

At minimum the engagement should state what work is included (for example contract review, entity governance, and employment questions) and what falls outside a general retainer (litigation, regulatory defense, and M&A are commonly carved out and billed separately); the fee structure, whether flat monthly retainer, hourly, or fixed fee per project; the billing cycle and expense responsibility; and the notice period to end the engagement. If any of these is missing or vague, ask before you sign, not after the first invoice. Undefined scope is where both surprise bills and coverage gaps come from.

How should founders compare a startup lawyer, outside general counsel, and specialist counsel?

A startup lawyer or outside general counsel arrangement is the recurring, context-carrying relationship that handles the everyday legal operating pattern: formation, contracts, hiring questions, and financing readiness. Specialist counsel is brought in for defined matters that sit outside that pattern, such as litigation, regulatory defense, complex M&A, or patent prosecution. The two are complements, not competitors; what you want to confirm is that your primary counsel knows when to bring in a specialist and coordinates it cleanly. For the underlying model choice between outside GC, a law firm, and in-house, see the companion comparison article in this series.

What red flags should founders watch for when evaluating startup counsel in Maryland, DC, or the DMV?

Behavioral signals include no clear strategy after an initial consultation, repeated lateness during the courtship phase, jargon-heavy communication, and any inconsistency between what you are told and what turns out to be true. Substantive gaps matter more: counsel who cannot describe a recurring legal cadence, gives a vague or confidently-wrong answer on Maryland, DC, and Virginia licensure, treats AI, vendor, and data risk as generic boilerplate, cannot distinguish company-side fundraising from investment-fund formation, has no process for keeping a diligence file clean over time, or promises broad multi-state coverage with no local-counsel coordination plan. None is disqualifying alone; a pattern is a signal to keep looking.

What legal work should be organized before investor or enterprise diligence, and what does counsel's process tell you?

Before a raise or an enterprise sale, expect to show organized board consents and meeting records, cap table records with every option grant, SAFE, and prior round on consistent terms, documented IP assignments from everyone who touched core technology, and key customer and vendor contracts available for review. The selection signal is whether prospective counsel maintains this continuously or assembles it in a fire drill each time. Counsel who track approvals, equity, IP assignments, and contract positions over time hand you a file that already holds up when a lead investor's lawyers or an acquirer's counsel start reading; counsel who do not leave you rebuilding it under deadline.

Startup Legal Counsel in the DC-Baltimore Region: What Founders Should Look For

The DC-Baltimore region has no shortage of attorneys willing to say they work with startups. What it has a real shortage of is a clear way for founders to tell the difference between counsel who can move at your speed and counsel who has not yet built pattern recognition around your stage, sector, or financing model. This article is that evaluation framework: what to look for, what to ask, and the region-specific licensure questions that change the calculus in Maryland, DC, and Virginia.

If you've already decided you need outside counsel, the next decision is harder than it looks: which one. Founders in the DC-Baltimore region are choosing among boutique startup practices, regional firms, and national firms with a DMV office, and the marketing on all three sounds nearly identical. Everyone says "startup-friendly." Everyone says "responsive." The criteria that actually separate a good fit from a bad one rarely show up on a firm's homepage, and they compound over a multi-year relationship in a way a bad hire in most other vendor categories does not.

The goal here is not to tell every founder to hire the same kind of lawyer, and it is not another explanation of what outside general counsel is. It is a founder selection framework built around the right question. The test is not whether a lawyer says they work with startups. It is whether counsel can actually handle the legal operating pattern a DC-Baltimore company runs on: entity formation and governance, commercial contracts, financing readiness, the employment-adjacent questions that arrive with your first hires, IP ownership, data, privacy, and AI vendor risk, and the jurisdictional limits that come with operating across Maryland, DC, and Virginia. Everything below is about testing for that fit before you share confidential facts, rely on informal advice, or assume a short introductory call means counsel has been retained.

This article does not cover what outside general counsel does in this region (that's the local service guide), which model fits your stage (that's the model-comparison anchor), what it costs (that's the cost article), or when to make your first legal hire (that's the timing article). If you're still working out what the role itself involves, our outside general counsel practice page walks through it. This one answers a narrower question: given that you need outside counsel, how do you actually evaluate and choose the right one for a DC, Maryland, or Baltimore-based company?

What makes the DC-Baltimore region different when choosing startup counsel?

A few things stack up here in a way they don't in a more uniform market. The region spans three separate legal jurisdictions, Maryland, DC, and Virginia, each with its own bar admission rules and corporate statutes, so a founder whose team sits across Bethesda, downtown DC, and Tysons is quietly asking one attorney to either cover all three or coordinate across them well. It also concentrates heavily in a handful of sectors, cybersecurity, government technology, defense-adjacent work, regulated markets, research-institution spinouts, biotech, and a fast-growing AI cluster, where counsel needs baseline fluency in government contract terms and dual-use technology issues that a generalist elsewhere might treat as an edge case. Many of these companies also sell into enterprise and government buyers early, so their contracts get read by sophisticated procurement and security teams sooner than a typical consumer startup's would. And because the market is smaller and more relationship-driven than New York or the Bay Area, referral and reputation signals travel faster and carry more weight.

None of that changes the fundamentals of good counsel selection. It sharpens the stakes. The real divide is not general startup familiarity versus none. It is between counsel whose work merely gets you to the next step and counsel whose work holds up later: when a lead investor's lawyers run diligence, when an enterprise or government customer's procurement and security teams review your contracts and security exhibits, or when an acquirer's counsel reads your cap table, IP assignments, and board record line by line. In this region the cost of getting counsel selection wrong tends to show up sooner, in a jurisdictional gap you didn't know you had, or a government-adjacent contract term nobody flagged.

What criteria actually separate good startup counsel from a generic corporate lawyer?

Six things do most of the differentiating work: stage-specific expertise, engagement letter clarity and fee structure, responsiveness and communication, referrals and track record, firm structure (boutique versus national), and region-specific sector knowledge. What's uncommon is a founder checking them systematically before signing, instead of defaulting to whoever was easiest to reach first or came recommended by a single acquaintance. The sections below work through each one, then close with the licensure mechanics specific to Maryland, DC, and Virginia, a red-flag list, and an interview checklist.

What should you look for: stage-specific expertise?

The single biggest differentiator between counsel who fit a startup and counsel who don't is whether they have a real track record with the specific work your stage produces: entity formation, SAFE or convertible note rounds, priced equity closings, and the cap table mechanics of each. A general corporate attorney can competently handle a one-off contract dispute or formation. What they often haven't built is the pattern recognition that comes from seeing the same negotiation, the same investor term, or the same cap table mistake across dozens of similar companies.

The test here is specific, not general. Don't ask "do you work with startups?" Ask for representative experience with entity formations, SAFE or convertible note rounds, priced equity financings, and cap table issues, and ask whether the attorney personally handled that work or supervised it directly, rather than pointing to the firm as a whole. A red flag worth naming: counsel who only bills routine startup matters hourly with no flat-fee or retainer option at all. That often signals a practice that isn't structured around recurring startup work, even if it takes startup clients occasionally.

What should you look for: engagement letter clarity and fee structure?

An engagement letter is a proxy for how organized and founder-friendly a practice actually is, so read it closely before you sign. At minimum, it should state what work is in scope (contract review, entity governance, employment questions) and what falls outside the retainer (litigation, regulatory defense, and M&A are commonly carved out and billed separately). It should state the fee structure, flat monthly retainer, hourly, or fixed fee per project, along with the billing cycle, expense responsibility, and the notice period to end the engagement.

On fee structure, the question isn't "what's the number." It's whether the structure matches how much legal work you actually expect. A flat retainer works when your needs are recurring and predictable enough to size in advance; hourly or fixed-fee-per-project tends to fit occasional matters better. Many early-stage companies start with a fixed-fee formation package plus hourly work for the occasional question, then move to a retainer once monthly work is consistent enough to justify it. For the actual ranges and how to model them, the cost article in this series covers that; this one is about the structure, not the price tag.

What should you look for: responsiveness and communication?

Responsiveness is one of the few criteria you can test before you sign. During evaluation, ask a real, specific question, not a hypothetical, and note how quickly and how clearly the attorney responds. For routine questions, many startup-focused engagements define an expected response window, often same-day or next-business-day depending on urgency, scope, and the terms of the engagement. If you're waiting a week for a reply during the sales process, when a firm is trying to win your business, that's still a signal about what to expect once you're a client.

Ask directly who will handle your day-to-day matters. In larger practices, a senior attorney often runs the pitch meeting while an associate handles the ongoing work. That's not automatically a problem, but you should know it going in and meet the person who will actually be answering your calls.

What should you look for: referrals and track record?

Founder referrals, investor references, and accelerator recommendations are more reliable signals than any marketing page, because they reflect lived experience rather than positioning. In the DC-Baltimore region, ask other founders at local accelerators, investor groups, and co-working spaces who they use and why. A startup-focused attorney may also be able to identify categories of other professionals a founder should consider, such as accountants, tax advisors, insurance brokers, or regulatory specialists, while keeping any referrals separate from legal judgment and professional-independence obligations.

Check track record directly rather than taking it on faith. Ask whether the attorney can provide references, testimonials, public representative matters, or founder introductions where the client has consented, and ask specific questions when you can: how responsive was counsel during a time-sensitive matter, did they flag issues proactively or only when asked, and would the founder hire them again for the next round.

What should you look for: boutique versus national firm, the trade-off?

This is a genuine trade-off, not a question with one right answer. Boutique and specialized startup practices tend to compete on personal attention, founder-friendly terms, and lower relative cost, because they're built around a narrower client base and don't carry the overhead of a national platform. National firms tend to offer breadth, bench strength across specialties, and the ability to carry a company through its full lifecycle, including later-stage matters like complex M&A or a public offering that a boutique may need to refer out.

For a seed or early Series A company, the attention a boutique offers frequently matters more day to day than the breadth a national firm can offer for events that may be years away. As a company scales and matter complexity grows, particularly around financings with sophisticated investor counsel across the table, that calculus can shift. Neither model is automatically right; it's a question of what your company needs at its current stage, not what sounds more prestigious.

What should you look for: region-specific sector knowledge?

The DC-Baltimore region concentrates in a specific set of sectors: technology broadly, a growing AI cluster (the University of Baltimore launched an AI startup accelerator in 2026 with its first cohort of eight companies), cybersecurity, government-adjacent technology, defense, federal research and development, and healthcare and life sciences. If your company sits in any of these, counsel fluency in government contract terms, dual-use technology issues, security clearance questions, and AI vendor and data-provenance risk isn't a specialty add-on. It's a baseline expectation.

A national firm without meaningful DMV sector experience may not treat these as routine risks the way counsel embedded in the region does. Probe it directly in an interview: has this attorney actually reviewed government contract terms or AI vendor agreements with data-provenance clauses recently, or is this the first time the question has come up.

Licensure and multijurisdictional practice: Maryland, DC, and Virginia coordination

This trips founders up more than any other selection criterion, because it's invisible until it isn't. Maryland, DC, and Virginia each have separate bar admission rules, and none of them automatically covers the other two.

Maryland. Maryland has separate rules governing admission of out-of-state attorneys, including procedures for attorneys admitted in other US jurisdictions. A lawyer admitted in DC or Virginia should not be assumed to be authorized to handle Maryland-specific legal work unless they are admitted in Maryland or working through an authorized pathway. If your company needs Maryland-specific governance or formation work, confirm how your counsel is authorized to do it before you rely on the advice.

District of Columbia. DC Rule 49 addresses the unauthorized practice of law and provides several exceptions, including limited pro hac vice appearances. The rule also makes clear that practice carried on in DC can require DC Bar admission even where the substantive law is not DC law, unless an exception applies. If your company is DC-formed or DC-headquartered and your counsel isn't DC-admitted, ask how they are handling Rule 49 for your ongoing work.

Virginia. Virginia permits admission without exam for qualifying attorneys, generally those who have been actively engaged in the practice of law for at least three of the five years immediately before they apply, and it separately permits registered in-house counsel arrangements. There is no automatic reciprocity across Maryland, DC, and Virginia; a Maryland or DC license does not, by itself, authorize Virginia-specific practice. If your team has engineering staff in Northern Virginia, or you're forming a Virginia entity, you generally need either Virginia admission or coordination with Virginia-licensed counsel.

The practical takeaway: don't assume a single license covers your whole footprint. Ask directly, upfront, how the attorney handles matters in a jurisdiction where they aren't personally admitted, and whether that coordination is built into their standard practice or something you'll be figuring out mid-crisis.

For context on where this firm fits: Consilium Law is admitted to practice in Maryland and the District of Columbia. For Virginia-specific legal matters, including Virginia entity formation, Virginia employment issues, Virginia litigation, or legal advice governed primarily by Virginia law, the appropriate path may require Virginia-admitted counsel or coordinated co-counsel involvement. Founders should confirm jurisdictional coverage in writing before assuming that any one attorney or firm can handle all Maryland, DC, and Virginia matters directly.

Red flags when evaluating startup counsel in Maryland, DC, or the DMV

A few patterns are worth treating as warning signs during evaluation, individually not disqualifying, but worth weighing together. Start with the behavioral signals:

No clear strategy after an initial consultation. If the attorney can't articulate a rough plan for your entity structure, financing posture, or IP setup after hearing your situation, that's a gap in preparation or expertise.
Repeated lateness or rescheduling. One reschedule happens to everyone. A pattern of it during the courtship phase, when a firm is presumably on its best behavior, tends to forecast the working relationship accurately.
Communication that leans on jargon without explanation. If every answer requires a follow-up question just to understand the first answer, that's a communication-style mismatch worth naming before you sign.
A sense that they aren't genuinely invested. Hard to quantify, easy to feel. If the attorney seems to be going through the motions rather than engaging with your business, trust that instinct.
Any inconsistency between what you're told and what turns out to be true. Whether it's about availability, cost, or scope, a single inconsistency is worth a direct follow-up. A pattern of them is a reason to keep looking.

Beyond behavior, watch for substantive gaps that tell you counsel is not built for the recurring, diligence-grade work a growth company generates:

Cannot explain a recurring legal cadence. If counsel can only describe one-off projects and has no view of what ongoing legal work looks like month to month, that is a mismatch for a company that will generate recurring questions across hiring, contracts, and financing.
No clear answer on jurisdictional limits. A vague or confidently-wrong answer about Maryland, DC, and Virginia admission is worse than a plain "I'm admitted in Maryland and DC and coordinate Virginia counsel for Virginia-specific matters." You want the honest version.
Treats AI, vendor, and data risk as generic boilerplate. If training-data provenance, audit rights, and data-processing terms get waved off as standard, counsel is not reading the paper your enterprise and government customers, and their security teams, will read closely.
Cannot distinguish company-side fundraising from investment-fund formation. A founder raising a priced round, a SAFE, or a friends-and-family round is doing company-side securities work, not forming an investment fund. Counsel who blurs the two may not be sized for either.
No process for maintaining a diligence file over time. Board consents, cap table records, and IP assignments that only get assembled in a fire drill before a raise are a warning sign. The value of ongoing counsel is that the record is already clean when a term sheet or an acquirer arrives.
Engagement letter that does not define what is in scope and out of scope. This belongs on the red-flag list as much as it belongs in the fee-structure discussion above. Undefined scope is where surprise bills and coverage gaps both come from.
Promises broad coverage across many states without a local-counsel coordination plan. Confident multi-state coverage with no mention of how out-of-jurisdiction matters actually get handled is a licensure risk dressed up as a convenience.

For a startup, reliability matters more than in most vendor relationships, because you'll rely on this person repeatedly at moments that carry real consequences: a financing closing, a key hire, a customer contract under time pressure.

Questions to ask before hiring: the founder interview checklist

A structured set of questions surfaces fit or mismatch faster than an open-ended conversation. Bring these, or a version of them, to every serious conversation with prospective counsel:

What representative experience do you have with entity formations, SAFE or note rounds, and priced financings, and did you personally handle that work or supervise it directly, rather than pointing to the firm's general experience?
What is your standard response time for routine questions, and what's the protocol for something urgent?
Do you represent other startups as a core part of your practice, or as an occasional add-on to general corporate work?
Who will actually be doing the day-to-day work on my matters, and can I meet that person now?
What's in your engagement letter: scope, fee structure, expenses, and termination notice?
Are you licensed in Maryland, DC, and Virginia? If my company needs work in a jurisdiction where you aren't admitted, how do you handle that coordination?
Do you have direct experience with government-adjacent customers, federal contracting terms, or AI vendor agreements, if relevant to my business?
Do you manage recurring legal work on an ongoing basis, or handle discrete projects as they come up? What is included in a monthly outside general counsel arrangement, and what is scoped and billed separately?
How do you track board approvals, cap table and equity approvals, IP assignments, and contract positions over time, so the record holds up when an investor or acquirer runs diligence?
What is your process for customer contracts, vendor agreements, AI tools, and data-processing terms?
When do you bring in specialist counsel, and how do you coordinate it?
Can you provide references, testimonials, or public representative experience, subject to client consent and confidentiality obligations?

Decision Framework

Have you asked for representative experience, not general claims? "What SAFE rounds have you personally handled or supervised" produces a different, more useful answer than "do you work with startups."
Does the engagement letter match what you were told verbally? Compare the written scope and fee structure against what was discussed on the call. A mismatch, even a small one, is worth raising before signing.
Have you tested responsiveness with a real question, not a hypothetical? The sales-process response time is useful evidence, but the engagement letter should still define the communication expectations you'll rely on.
Does counsel have a real answer for your multijurisdictional footprint? If your team spans Maryland, DC, or Virginia, an attorney who hasn't thought about this before your question is a gap, not a technicality.
Have you checked at least one reference you didn't get from the attorney directly? A founder network recommendation carries more information than a reference the attorney selected and provided.

Audience-Specific Implications

For Founders and CEOs

Counsel selection is a decision you'll live with across your company's most important moments, financings, key hires, customer contracts under deadline pressure, so treat it with the diligence you'd apply to a key hire, not the urgency of picking a vendor off a list. The stage-expertise and responsiveness criteria matter most to you, because you're the one calling with the urgent question at 6 p.m. before a term sheet deadline.

For CFOs and Finance Leads

The engagement letter clarity criterion intersects most directly with your world. A fee arrangement that doesn't clearly define in-scope versus out-of-scope work, or that lacks a billing cycle and termination notice, creates budgeting uncertainty that shows up later as an unplanned invoice or a scope dispute. Read it with the same scrutiny you'd apply to any recurring vendor contract before it goes to signature.

For COOs and Operators

The multijurisdictional coordination question matters most if your team's footprint spans more than one of Maryland, DC, or Virginia, whether through remote hires, a satellite office, or expansion plans already on the roadmap. Confirm during evaluation, not after a jurisdiction-specific issue surfaces, how prospective counsel handles matters outside their home jurisdiction.

Practical Takeaways

Ask for representative experience, personally handled or directly supervised, not firm-level claims. If a prospective attorney can't point to representative entity formations, SAFE rounds, or priced financings they handled or supervised directly, treat "we work with startups" as marketing language until proven otherwise.
Read the engagement letter for what's excluded, not just what's included. Before your next scheduled call with prospective counsel, confirm litigation, regulatory defense, and M&A carve-outs are stated explicitly, since these are the matters most likely to generate a surprise bill later.
Test responsiveness with a real question during the sales process. Send one specific, substantive question before you sign, and measure both the speed and the clarity of the answer; that response is useful evidence, though the engagement letter should still define the communication expectations you'll rely on.
Confirm who will actually do your work, by name, before you sign. If a senior attorney runs your pitch meeting, ask whether an associate will handle ongoing matters, and ask to meet that person before your engagement starts.
Check at least one reference you sourced independently. A recommendation from your own accelerator or investor network tells you more than a reference the attorney selected; where an attorney provides references, expect that to be subject to client consent and confidentiality obligations.
Confirm multijurisdictional coordination in writing if your footprint spans Maryland, DC, or Virginia. Ask how the engagement handles matters outside counsel's home jurisdiction, and get the answer before your next hire or lease pulls your operations into a new state.
Weigh the boutique-versus-national trade-off against your next 12 months, not your eventual exit. A boutique's attention and responsiveness usually matters more at seed and early Series A than a national firm's later-stage bench strength; revisit the calculus as your matter complexity actually grows, not preemptively.
If your sector touches government contracting, defense, or AI, ask for direct evidence of that experience. A generic "we handle tech companies" answer is not the same as recent, specific experience with government contract terms or AI vendor data-provenance clauses.

Closing Perspective

What I keep coming back to is this: founders spend weeks diligencing a Series A term sheet and then pick outside counsel off a single warm introduction and a good first call. The discipline should run the other direction. Counsel selection compounds over years in a way most vendor decisions don't, and the criteria that actually matter, representative deal experience handled or supervised directly, a clear engagement letter, tested responsiveness, and a real answer on multijurisdictional coordination, are all things you can check before you sign, not things you discover after a missed deadline.

None of this requires finding the single best attorney in the region, because that framing doesn't hold up anyway. It requires finding the right fit for your stage, your sector, and your footprint, and confirming that fit with specific questions rather than a general impression. The founders who get this right treat the interview itself as the diligence exercise it is. The next test won't be the first invoice. It'll be the first time you need a fast, clear answer under real pressure, and find out whether the person on the other end of the phone actually shows up.

This article is for informational purposes only and does not constitute legal advice. Reading this article, contacting Consilium Law, or submitting information through this website does not create an attorney-client relationship. An attorney-client relationship is formed only after Consilium Law confirms the engagement in writing. Consilium Law practices in Maryland and the District of Columbia; Virginia-specific matters may require Virginia-admitted counsel. References to "startup counsel," "startup-focused counsel," or similar terms are descriptive only and do not imply certification as a legal specialist. Every company's situation is different, and founders should consult counsel admitted in the applicable jurisdiction before making legal or compliance decisions.