Audrey · Corporate Structure Decision — DBA Trap
AUDREY · BUSINESS IDENTITY · 12 MAY 2026
Companion to audrey_entity_twilio_2026-05-12.md. Same series, different cut: that one was “how do we pass Twilio KYC”; this one is “should the entity that submits be Audrey Design Inc or a separate Dogwood entity, and what’s the gotcha if we pick wrong”.
TL;DR
- Near-miss: almost submitted Twilio toll-free verification thinking the corporate structure choice was cosmetic. It’s not. Without a properly-filed DBA, submitting a brand-named number under a different legal entity reads as impersonation to commercial-database KYC vendors — even when ownership is legitimate.
- Three structural options for one founder running multiple brands: holding company, single entity + DBAs, independent entities. Single entity + DBAs is the right default until a brand takes outside investment / develops materially different liability profile / needs independent sale.
- Concrete action: for Audrey Design Inc to be the master entity that also covers Dogwood House (and future brands), file a NY Certificate of Assumed Name (“Dogwood House” as a DBA of Audrey Design Inc) at https://dos.ny.gov/forms-publications. ~$25, online, ~2-4 months to propagate to commercial-database aggregators before KYC stops flagging it.
- Caveat: structural decisions warrant accountant + attorney consult (~$500-1500 one-time). LLM framing for operational clarity; final structure is a legal decision.
What happened
While drafting the runbook for Twilio’s toll-free entity submission earlier today, Dan asked: “can an entity like Audrey Design Inc be well within its remit to be the master entity, for a venture like dogwood.house?” Implicit assumption: corporate ownership is enough; the brand name on the Twilio submission is cosmetic.
It isn’t. The trap:
Audrey Design Inc submitting a 1-800 number for “Dogwood House” looks like impersonation to commercial-database aggregators (LexisNexis, D&B) — even if the ownership is legitimate — because there’s no public record connecting Audrey Design Inc to the brand name “Dogwood House” unless a DBA has been filed and propagated.
The KYC vendors don’t know about your corporate intent. They check whether the entity name on the submission has any public-record claim to the brand name on the customer-facing service. The DBA filing is what makes that public-record claim. Without it, the submission has the same legal signature as an impersonator using a brand they don’t own.
This was almost missed. The dev report captures it so future-me doesn’t make the same mental error.
Root cause — the three structures
| Structure | What it is | Audrey-as-master verdict |
|---|---|---|
| Holding company | A parent (“Dan Sellars Holdings LLC”) owns Audrey Design Inc + Dogwood House LLC as subsidiaries | Overkill for solo-founder portfolio without outside investors. Adds tax / compliance / accounting overhead disproportionate to current scale. |
| Single entity + DBAs ✅ | Audrey Design Inc IS the master entity. Other brand names (Dogwood House, future brands) filed as DBAs of Audrey Design Inc via NY Certificate of Assumed Name. | Recommended default. Lowest overhead, full legal coverage, clean KYC submissions once DBAs propagate. |
| Independent entities | Each brand its own LLC; you own each via personal capacity; no parent | More liability isolation than option 2 but more paperwork. Falls between the other two. |
Sub-decision when picking option 2: brand-naming each DBA carefully. NY’s Certificate of Assumed Name filing is searchable in the public DOS records — pick the exact spelling the brand uses commercially. “Dogwood House” vs “Dogwood House, LLC” vs “Dogwood House Inc” all look like different entities to KYC vendors.
Action plan — Audrey Design Inc as master entity
1. Confirm Audrey Design Inc canonical legal name (prerequisite for the rest)
Per the entity-submission runbook (audrey_entity_twilio_2026-05-12.md), the NY DOS public inquiry lookup at https://apps.dos.ny.gov/publicInquiry/ returns the registered legal name exactly as recorded. Capture it before filing any DBA — case-sensitive matching matters for the propagation chain.
2. File NY Certificate of Assumed Name for each operating brand
For each brand operated under Audrey Design Inc:
Action: at https://dos.ny.gov/forms-publications, locate “Certificate of Assumed Name (DOS-1338)”. File online — ~$25 per assumed name; effective immediately on filing; public record from day one.
Capture per filing: - Filing date - Assumed name (exact commercial spelling) - Filing receipt number - County of filing (NY filings publish at the state level + the county of operation)
Likely first filings for Dan’s portfolio:
- DOGWOOD HOUSE (covers dogwood.house brand operations)
- Future brands as they materialise
3. Wait for commercial-database propagation
DBAs filed at NY DOS feed into: - D&B (via standard NY DOS data feeds — ~2-4 weeks if the parent entity already has a D-U-N-S; longer otherwise) - LexisNexis Risk Solutions, Experian Business (downstream of D&B + DOS feeds; ~2-4 months total)
During the propagation window: any KYC submission can still go through under Audrey Design Inc as the legal entity, with the brand name used only at customer-facing layers (IVR, email templates, marketing). Don’t put the brand name into a “Legal Entity” field until propagation confirms.
4. Update Audrey’s D-U-N-S record with the DBA aliases
Once the D-U-N-S is issued (per the parallel entity-submission runbook):
- Log into D&B’s update portal (https://www.dnb.com/myaccount)
- Add the assumed-name aliases as “DBA” entries on Audrey Design Inc’s record
- This makes the aliases first-class in D&B’s records, which most KYC vendors then trust
5. Re-attempt the Twilio toll-free submission with the brand name
Once the DBA shows up in either D&B or the LexisNexis Consumer Disclosure pull, retry the Twilio submission with brand name in the customer-facing fields and Audrey Design Inc in the legal entity fields. The DBA is what connects them in public records — KYC verification then resolves cleanly.
Why this matters beyond Twilio
The same DBA-propagation gate gates every B2B/regulatory touchpoint where brand identity ≠ legal entity:
| Touchpoint | Behaviour without DBA | Behaviour with DBA |
|---|---|---|
| Twilio toll-free verification | Flagged as impersonation; null verification | Resolves cleanly to Audrey Design Inc with brand alias |
| Stripe Atlas for a sub-brand | Requires separate legal entity | Accepts the DBA; single Stripe account covers brands |
| Wholesale buyer portal vendor onboarding | Buyer’s compliance flags the mismatch | DBA on record matches; onboarding passes |
| Bank account in the brand’s name | Bank requires separate entity OR DBA filing | DBA filing satisfies bank KYC |
| Insurance policy in the brand’s name | Insurer requires consistent identity | DBA filing connects coverage to legal entity |
| Trademark registration for the brand | Filed under legal entity (Audrey Design Inc) with brand as “first-use” name | Same — DBA filing strengthens the trademark claim |
One $25 NY filing per brand unblocks all of them simultaneously.
When to evolve beyond “single entity + DBAs”
Triggers that justify upgrading the structure:
- Brand takes outside investment. Investors want corporate isolation — split that brand into its own entity, or roll the whole portfolio under a holding company.
- Liability profile materially diverges. Dogwood handles other people’s pets (real injury risk); Audrey sells silk scarves (low injury risk). If dogwood ever has a serious claim, Audrey assets are exposed under the shared-entity model. Worth pre-emptively splitting if dogwood scales to multiple boarding locations.
- Independent sale path. Selling dogwood without selling Audrey requires either a pre-existing separate entity OR a complicated asset-only sale + brand transfer.
- State-residency differences. If a brand operates primarily in another state with different tax / regulatory rules, separate entity may be more efficient.
Until any of those fire, single-entity + DBAs is the right structure. Don’t split prematurely — splitting is one-way (logistically; you can re-merge but it’s painful), and the operational tax of multiple entities is real.
Open items for audrey
- [ ] Confirm Audrey Design Inc canonical NY DOS legal name + DOS ID (depends on
audrey_entity_twilio_2026-05-12.mdstep 1) - [ ] Decide which brand names to file as DBAs (likely:
DOGWOOD HOUSEfirst; others as they’re brought online) - [ ] File NY Certificate of Assumed Name for each (online, ~$25 per filing)
- [ ] Add DBAs to Audrey Design Inc’s D-U-N-S record after D-U-N-S is issued
- [ ] Retry Twilio toll-free submission with brand-name-in-customer-fields + Audrey-Design-Inc-in-legal-fields after DBA propagates
- [ ] Decide: now, or after talking to accountant/attorney? Recommend a quick 30-min consult before filing — confirms the structure choice is right for tax + liability situation.
Portability — applies to dogwood + future client work
Same shape applies any time a portfolio operates multiple brands under one founder:
- Dogwood, when more brands eventually layer onto the boarding operation (e.g., “Dogwood Provisions” for retail, “Dogwood Method” for training), DBAs under Dogwood House LLC
- Future agency clients, when they operate multiple brands themselves and ask “should we structure this as one entity or many?” — same three options, same default
- Reference for new portfolio surfaces — every time we ask “should this brand have its own entity?”, revisit the four upgrade triggers; default answer is “no, DBA is fine”
Linked memories
reference_corporate_structures_portfolio.md— new today — the durable framework + decision criteriaproject_audrey_business_identity.md— the identity stack this structure decision sits atopaudrey_entity_twilio_2026-05-12.md— the companion runbook (Twilio-specific submission steps)feedback_thin_edge_canonical_source_uplift.md— same canonical-source-of-truth-plus-surfaces pattern, applied to legal layer instead of technicalfeedback_just_in_time_permission_grants.md— same minimal-permanent-surface instinct, applied to corporate paperwork