Honest answers
to the questions
you’d actually ask.

A Tab is an independent operating company chartered through TabTab Studio, with the Chair holding majority ownership and TabTab’s AI Agents Operating System running its day-to-day operations. It has its own customers, its own bank account, and its own future.

Pre-incorporation, a Tab operates as a product line under TabTab LLC during a validation phase, with the Chair’s equity contractually committed at the 65/25/10 split. Once the Tab hits its incorporation trigger — typically validated revenue or a time threshold — it incorporates as a Delaware C-corporation and the Chair receives their stock. Most of our portfolio Tabs operate this way today.

What makes a Tab different from a normal company isn’t the legal structure — that’s standard. It’s the operating model: instead of hiring engineers, marketers, salespeople, and support staff, the Tab runs on TabTab’s coordinated AI agents. You provide judgment and accountability. The agents provide execution.

No, and that’s deliberate. Tabs operate under TabTab LLC as product lines during the validation phase, typically the first 90–180 days. This means we skip the legal infrastructure (Delaware filing, registered agent, EIN, board agreement, separate bank account) until the Tab proves it’s worth that overhead.

During this phase, you sign a Chair Agreement — a written contract that commits TabTab LLC to grant you 65% of the Tab’s stock at incorporation, with TabTab Studio holding 25% and 10% reserved for future hires or contributors. Your equity is contractually real even though the entity isn’t formed yet.

When the Tab hits its incorporation trigger — validated revenue and time thresholds defined in your Chair Agreement, or your request as Chair — we form the Delaware C-corp, assign IP and contracts into the new entity, and grant you actual stock. The QSBS clock starts at that point.

Traditional studios like Atomic, High Alpha, or Pioneer Square Labs spend $500K–2M per company building MVPs with engineering teams, then recruit a CEO who runs the operation full-time. They take 30–50% equity for that work.

TabTab does the same job for two orders of magnitude less because AI agents replace the build team. You bring $25K and your knowledge instead of millions and a full-time founder commitment. We take a smaller equity stake because our cost is lower.

The simplest way to think about it: traditional studios are designed for people who want to be CEOs. TabTab is designed for people who want to be Chairs.

$25K is the actual cost to launch a Tab — we didn’t pick it for marketing. It breaks down roughly as:

• $4,000–6,000 for dedicated hardware (Tab·Stack per the Platform page — the home of your Tab’s local LLMs)
• $8,000–10,000 for software development and agent build
• $4,000–5,000 for TabTab OS setup and integration
• $2–3K for initial APIs (Stripe, Twilio, email infrastructure, specialized services)
• $1–2K for the Chair Agreement, Platform License, and legal templates
• $1–2K reserve for early operations

Delaware C-corp formation costs are deferred to incorporation — paid from the Tab’s operating revenue at that point, not from your initial $25K.

$25K is also a deliberate filter. It’s enough to signal real commitment. It’s small enough that the right person — a senior operator with risk capital — won’t blink. It’s large enough that we don’t get applications from people exploring whims.

Our standard split is 65% to the Chair, 25% to TabTab Studio, 10% reserved pool for future hires or contributors. Pre-incorporation this is a contractual commitment in the Chair Agreement; post-incorporation it becomes actual stock.

Your 65% is for the $25K cash investment, the structured knowledge transfer (interviews, documents, processes), and your ongoing role as Chair. TabTab Studio’s 25% is for serving as your full technical co-founder during the unfunded early years — running the entire cloud infrastructure, deployments, integrations, payment processing, App Store relationships, and ongoing platform work that the AI agents can’t do alone.

The 25% reflects real, ongoing technical labor during the period when no one else would do it. After your Tab raises Series A and can hire its own technical team, TabTab Studio’s role evolves (see N° 10b). The equity stays — it was earned during the early high-risk years.

If the Tab raises outside capital later, both sides dilute proportionally. We negotiate pro-rata rights so we can maintain our position through future rounds when warranted.

For Tabs in unusual situations — heavy regulatory burden, deeper TabTab involvement, atypical capital needs — we sometimes use a different split. We’ll always discuss this before formation.

The agents do execution. TabTab Studio does infrastructure and platform engineering, continuously, for the life of your Tab.

Every Tab has a real cloud architecture that needs to be built, deployed, and maintained. The AI agents in TabTab OS can write code, draft marketing copy, send outreach, qualify leads, and handle support — but they cannot deploy to Vercel, provision a Neon Postgres database, configure AWS S3 storage, set up Google and Apple OAuth, submit to the App Store, integrate Stripe and RevenueCat, manage LLM API keys, or build custom MCP connectors for industry-specific vendor APIs.

That work is ours. Specifically, TabTab Studio’s engineering team handles:

• Cloud infrastructure: Vercel deployments, database provisioning, storage configuration, monitoring, scaling
• Identity and authentication: OAuth setup with Google, Apple, and custom providers; certificate management; session handling
• Payments: Stripe configuration, RevenueCat for mobile, tax handling, refund flows, subscription logic
• App Store relationships: iOS and Android submissions, review responses, version management, compliance updates
• Third-party integrations: MCP connectors, vendor APIs, webhook plumbing, custom connectors for your industry’s tools
• LLM and API management: Keys, quotas, rate limit handling, vendor switching, model upgrades
• Security and compliance: Secrets management, access controls, audit trails, vulnerability response
• Platform development: Continuous improvements to TabTab OS itself, new agents, new capabilities

Domain experts who become Chairs don’t have to learn any of this. This is the technical co-founder you’d otherwise have to find, vet, and convince to join your company. It’s included in the Chair offer.

The 25% equity stake is compensation for this ongoing partnership — not just for setting up the Tab once. It reflects continuous engineering labor across the portfolio for the life of each Tab, until your Tab raises Series A and brings the work in-house (see N° 10b).

Honest answer: yes for most things, no for some, and the line is moving fast.

Agents work well today for: writing and shipping code, generating and testing marketing content, qualifying inbound leads, running outbound email campaigns, drafting contracts and documents, handling tier-1 customer support, basic financial reconciliation, and most internal operational tasks.

Agents struggle with: high-stakes negotiations, novel strategic decisions, deeply relational sales, complex multi-party legal matters, anything requiring physical presence, and judgment calls that require domain expertise.

That second list is what you’re for. The Chair is the human in the loop precisely where agents have gaps. TabTab’s design assumes this — agents handle the 90% they’re good at and escalate the 10% to you.

They will. Plan for it.

TabTab’s OS includes guardrails: agents operate within pre-defined authority levels, financial transactions above thresholds require Chair approval, customer-facing commitments are escalated before being made, and a continuous audit log captures every meaningful action.

When something goes wrong — and it will — there’s a defined escalation path. Most issues route to you as Chair within minutes. Infrastructure issues (deployments, integrations, vendor outages) route to TabTab Studio’s engineering team. Issues with broader portfolio implications (security incidents, novel legal questions, large-scale errors) come to TabTab Studio’s response team for parallel review.

For severe failures, the Tab carries E&O insurance starting at incorporation. The premium is small at this scale and is included in operating costs.

Otto is the on-machine AI mechanic that ships with every Tab. Think of him as the agents’ agent — a separate AI that lives on your Tab’s hardware and exists for one purpose: keeping the rest of the system running.

When TabTab OS needs an update, when an integration breaks, when an agent gets stuck in a loop, when something on the machine just needs to be fixed — Otto handles it. You don’t file a support ticket. You don’t wait on a vendor. You open a terminal, type hermes, and Otto goes to work.

Why does this matter? Because every other AI product in the world depends on someone else’s cloud being healthy. Your Tab depends on a machine on your desk and a mechanic who lives on it. That’s the difference between a tool and a company.

The Tab does. Always.

Pre-incorporation, customer contracts are held by TabTab LLC with explicit contractual assignment to the Tab’s eventual Delaware C-corp at incorporation. Post-incorporation, contracts are with the Tab directly. Customer data lives on the Tab’s hardware throughout. Customer relationships — including the email accounts agents use to communicate — belong to the Tab in either phase.

If you ever wound down the Tab, all of this would belong to the company’s shareholders, not to TabTab Studio. TabTab provides the operational platform. We don’t take customer data, don’t claim contracts, and don’t have any rights to customer relationships your Tab builds. This is contractually locked in the Chair Agreement and Platform License Agreement.

Realistically: 5–10 hours a week in the first 90 days, 3–5 hours weekly after that, with occasional spikes during major decisions or incidents.

The first 30 days are heavier — typically 10–15 hours a week — because we’re doing the structured knowledge transfer, you’re reviewing the initial agent configurations, and the Tab is launching. After launch, weekly demand drops as the agents settle into rhythm.

If your Tab finds product-market fit and starts scaling, your time may go up — not because the agents need more hand-holding, but because you’ll want to be more involved in the strategic upside. That’s a good problem.

If your Tab doesn’t find traction and gets wound down at the 6-month mark, your total time investment is typically 100–150 hours.

This is one of the most important questions, and the answer requires care.

Pre-incorporation, while the Tab operates under TabTab LLC, you are a contractually-committed future shareholder and an operational decision-maker — but you are not yet a director with formal fiduciary duties. Your liability during this phase is governed by the Chair Agreement: typically limited to your $25K commitment plus any specific obligations you accept in writing.

Post-incorporation, you become Chair and director of the Tab’s Delaware C-corp. You take on standard fiduciary duties — duty of care and duty of loyalty to the company and its shareholders. These are well-defined in Delaware law and are the same duties any corporate director carries.

The corporation itself shields you from most operational liability. If the Tab is sued because an agent sent an inappropriate email or processed a payment incorrectly, the Tab is liable, not you personally. This is what corporations are for.

You retain personal liability for: gross negligence in your duties, fraud, criminal acts, and (in some cases) tax matters. Standard D&O insurance covers most of the first category and is included in the Tab’s operating costs once incorporated.

The honest part: this is real legal exposure, not zero. We strongly recommend reviewing both the Chair Agreement and the formation package with your own attorney before signing. We’ll provide everything in advance and answer any questions they have.

Yes — once incorporated. Tabs are real Delaware C-corps with standard cap tables after incorporation, and can raise pre-seed, seed, Series A, or any later round on standard terms.

Pre-incorporation Tabs that find traction quickly enough to want to raise typically incorporate first (which is itself one of the incorporation triggers in the Chair Agreement), then raise on standard terms. The validation phase is short enough that this rarely creates friction.

The Platform License Agreement is structured to survive due diligence — it’s transferable, has locked pricing, and includes source-code escrow that triggers at Series A. Sophisticated investors review this and accept it.

Some Tabs will absolutely not need outside capital. AI-operated companies have radically lower burn rates than traditional startups; many can reach profitability on revenue alone within 12–18 months. The Tab makes this decision when the time comes.

If your Tab does raise, both you and TabTab dilute proportionally on the new round — standard mechanics. We negotiate pro-rata rights at formation so we can maintain position through future rounds when we choose to.

The relationship evolves into a different kind of partnership.

During the formation and validation phase — and through early growth — TabTab Studio is your full technical co-founder. We handle all the infrastructure described in N° 04b, alongside the AI agents handling execution. This is bundled into the monthly platform fee plus the 25% equity stake.

After your Tab raises Series A, you’ll have the capital to hire your own technical leadership — a Head of Engineering, a DevOps lead, or both. At that point, the typical path is for your Tab to bring infrastructure work in-house. TabTab Studio transitions out of operational engineering and continues to license TabTab OS as the platform substrate your company runs on.

Specifically:

• Trigger: Series A close (the formal funding event)
• Timeline: Transition completes within 6 months of Series A close
• Knowledge transfer: TabTab Studio’s engineering team works with your new technical hires for 4—8 weeks of dedicated transition — runbooks, secrets handover, vendor relationships, operational documentation. Included at no extra cost.
• Post-transition platform fee: Drops to a software-license-only tier (typically $500—$1,500/month) that covers TabTab OS itself but not engineering labor
• TabTab Studio’s 25% equity: Stays. It was earned during the unfunded years when we were your technical co-founder.

Tabs that prefer to keep using TabTab Studio’s engineering team after Series A can elect to do so on a retainer basis at market rates ($5K—15K/month depending on Tab complexity). Both paths are supported. The choice belongs to the Tab.

This two-stage model is intentional. It mirrors how venture-backed companies actually mature: in the high-risk unfunded years, you need a technical co-founder who’ll do the work without salary or guaranteed equity. Once the company is funded, you can build your own team. TabTab Studio’s value proposition is being that technical co-founder for the period when no one else would be — and getting compensated through equity for bearing that early risk.

Tabs can be wound down at any point with 60 days’ notice. The process is documented in the Chair Agreement (pre-incorporation) and Board Agreement (post-incorporation).

Wind-down before incorporation is simpler — there’s no entity to dissolve, just a product line to shut down, customers to notify, and the Chair Agreement to formally close out. Your $25K is largely spent at that point on hardware, software, and operations; remaining hardware is yours to keep or return for partial credit.

Post-incorporation, if revenue is below the agreed kill threshold ($5K MRR by month 6 is our default), winding down is straightforward: customers notified, contracts honored or transitioned, remaining cash distributed pro-rata to shareholders, hardware returned or sold, corporate dissolution filed.

If the Tab has revenue and you want to step away, you have options: recruit a replacement Chair (with TabTab’s consent), sell your equity (subject to standard transfer restrictions), or wind down voluntarily. We’ll work with you on whichever path makes sense.

You always keep the equity you’ve vested. Tabs that wind down still represent learning and reputation, not just sunk cost.

Fair question. The Platform License Agreement is structured so this doesn’t strand you.

The license is perpetual and irrevocable for the life of the Tab. Source code is held in escrow with a third-party agent. If TabTab discontinues operations, the escrow releases, and your Tab gets the source code to continue running independently.

This means your Tab’s continuity doesn’t depend on TabTab’s continued existence. It depends on your Tab and the codebase — both of which you have dedicated access to.

The realistic scenario is more like a slow degradation of feature development than a sudden shutdown. Even in that case, your Tab keeps running on the version it has.

You shouldn’t, if starting solo is the right path for you. Many of the people we talk to should just start their own company.

TabTab makes sense for people in a specific situation: you have a strong idea and deep industry knowledge, but you don’t want to (or can’t) commit full-time, and hiring a team yourself is too expensive and slow. The trade-off is straightforward — you give up some equity (35% — 25% to TabTab Studio and 10% reserved pool) and some operational control (the agents, not your team) in exchange for radically lower capital, time, and execution risk.

If you have $500K of risk capital, two years to commit full-time, and a network that lets you hire fast — go solo. You’ll keep more equity. If you have $25K, a few hours a week, and a real day job you don’t want to leave — TabTab is a path that didn’t exist before. Pick the structure that fits your reality.

A few categories where TabTab is a poor fit:

• Physical operations — restaurants, manufacturing, retail, logistics. Agents don’t move atoms.
• Highly relational sales — enterprise deals where personal trust over years is the moat. Agents can’t replace this.
• Heavily regulated industries requiring licensed humans for every customer interaction (some healthcare, certain legal services). Edge cases work; mainstream practice doesn’t.
• Capital-intensive businesses — biotech, hardware startups, anything needing $5M+ to reach first revenue. We’re built for software-leverage businesses.
• Network-effect plays requiring massive marketing spend to bootstrap. TabTab’s per-Tab budget can’t match a venture-funded competitor’s CAC.

The fit is strongest for: B2B software, productized services, niche SaaS, vertical AI applications, content/media businesses, and information products. If your idea is “the [specialized SaaS product] my industry needs but doesn’t have,” you’re probably in the right place.

Two streams.

First, monthly platform fees. Each Tab pays TabTab a flat monthly fee for platform access — typically $1–3K depending on usage tier. This is paid from the Tab’s operating revenue once the company is generating cash.

Second, equity in successful Tabs. Our 25% stake in each Tab compounds across the portfolio. Most Tabs won’t reach meaningful exits — that’s normal venture math — but the ones that do return many times what we put in. This is the long-term economic engine.

We don’t take per-token fees, don’t charge for individual API calls, don’t sell customer data, and don’t have hidden fees. The pricing is clean by design — we want every Tab’s incentives aligned with growth, not with managing usage.

The realistic outcome distribution, conservatively:

• ~60% wind down within 6–18 months without finding traction. Time investment recovered as learning; financial loss capped at $25K + a few hours weekly.
• ~30% become small businesses generating $250K–1M annually. Profitable, paying dividends, possibly running for many years. Not venture-scale, but a real asset.
• ~10% find meaningful traction — $1M+ ARR, growing 50%+ year over year. Some of these raise outside capital; some stay private and profitable; a few get acquired.

A successful 3-year Tab in the top 10% might look like: $3–5M in ARR, 200+ customers, profitable, 1–2 humans hired beyond the agents (often domain specialists for relationship-heavy work), and either preparing for Series A or generating substantial dividends to shareholders.

These are projections, not guarantees. We have six Tabs currently in market and the real distribution will only be clear at scale.

Several layers here.

Knowledge transfer IP: When you brain-dump your industry knowledge during onboarding, that IP is owned by your Tab — not by TabTab Studio and not by you personally. TabTab has a license to use it for operating that specific Tab, nothing more. We can’t take your industry insights and apply them to another Tab in the same vertical. Pre-incorporation, this is held by TabTab LLC under a fiduciary obligation to assign to the new entity at incorporation.

Customer data: Stays on your Tab’s hardware. Local LLMs handle most operations. When cloud APIs are used (occasional specialized work), data is sent only as needed and not retained by TabTab.

Product and code: The product your Tab builds belongs to the Tab. The TabTab platform is licensed to your Tab; the application code your Tab generates is yours.

If you’re operating in a regulated industry (HIPAA, GDPR, financial services), we have established compliance frameworks and can structure data handling appropriately. Talk to us during application about specific requirements.

Yes, with some structure.

Tabs can hire humans alongside the agents — we don’t pretend agents handle 100% of every situation. Common patterns include hiring a domain specialist for relationship-heavy sales, a regulatory expert for compliance-sensitive work, or a part-time finance contractor.

These hires are made by the Tab and paid from the Tab’s revenue. Equity for them comes from the 10% reserved pool established at formation. We’re happy to advise on standard offer terms and vesting structures.

If you want to bring a co-founder or partner into the Tab from the start, we’ll work with you to allocate equity from your 65% portion. The total equity given out at formation stays consistent — we just split your share differently.

What we discourage: hiring large teams that effectively turn the Tab into a traditional startup. If you want to do that, you’re better off going solo — the structure isn’t designed for it.