Costs
Organization plans examples: one two-founder plan
Explore organization plans examples through one two-founder startup plan: its decision table, founder responsibilities, vacant roles, and organization chart.
What to take away
- A two-founder plan still has to name who holds the last word on spending, hiring, and signing.
- The management team section can name two people and three vacant seats, each with a fill trigger.
- An organization chart for a business plan shows vacant roles as dashed boxes rather than blank space.
- Lenders read the authority split before they read the resumes.
- Deadlock rules belong in the operating agreement, not only in the plan.
A two-person team still needs a decision table
Two founders can draft a business plan in a weekend and still leave out the line a reader checks first: who decides.
When readers look for organization plans examples, one useful two-founder setup has two names, two titles, and an empty third box. That empty box is the problem, and it is also the fix.
Formation papers do not carry authority with them. The IRS LLC page sends membership and tax questions back to the states, so an LLC in Ohio and one in Wyoming start from different rules. For the example below, assume an Ohio LLC: the Ohio Revised Limited Liability Company Act (Ohio Revised Code Chapter 1706) governs its LLC framework, and the Ohio Secretary of State handles its Articles of Organization filing. Put founder authority and deadlock terms in the operating agreement, subject to the statute.
An organization plan for small business at this size stays short, but nothing inside it is optional.
Example: two founders, four decisions
Example plan: a fictional client-services studio organized as an Ohio LLC. Founder A is the Managing Partner, responsible for client delivery and contractor coordination; Founder B is the Finance & Growth Partner, responsible for budgeting, invoicing, and the sales pipeline. The four-row table below sets the final authority, backup, and trigger for signing contracts, hiring contractors, setting prices, and spending.
| Decision | Last word | Backup | Trigger that changes the rule |
|---|---|---|---|
| Sign contracts above $10,000 | Founder A | Founder B, in writing | After the first credit line closes |
| Hire contractors | Founder B | None | At 40 active clients |
| Set prices | Both, unanimous | Outside adviser breaks ties | After the first renewal cycle |
| Spend above $2,500 | Founder A | Founder B | Six months from signing |
A table survives review better than prose, because a lender can test each row against the operating agreement.
The management team section when the team is two people
For a startup organizational structure plan, give each founder four entries: title, day-to-day responsibilities, decision authority, and backup coverage. Here is how those entries read in this example.
Four answers per founder
- What this person owns outright
- What this person decides only after asking
- What this person cannot decide alone
- What would have to fail before the role changes hands
Founder A — Managing Partner
- Title:Managing Partner.
- Day-to-day responsibilities:Client delivery and coordination of contractor work.
- Decision authority:Founder A has the last word on contracts above $10,000; the table names the owner for contractor hiring, pricing, and spending.
- Backup coverage:Founder B is the written backup for the contract decision; use the table’s named backup for the other decisions.
Founder B — Finance & Growth Partner
- Title:Finance & Growth Partner.
- Day-to-day responsibilities:Budgeting, invoicing, and sales-pipeline follow-up.
- Decision authority:Follow the last-word assignment in each table row; the finance title does not override those assignments.
- Backup coverage:Use the backup named in each table row, with the contract backup recorded in writing.
The example leaves three seats vacant: operations, finance, and sales. Each line below names the work, who covers it now, and the trigger for filling the seat.
The SBA's plan guidance lists the management section as part of the standard set, so lenders expect it even from a company with no payroll.
Roles left vacant on purpose
Naming a vacant role is a schedule, not a confession of weakness.
Write each vacancy with four parts: the role, the tasks nobody covers today, the person absorbing them now, and the number that fills the seat.
- Operations Lead — vacant:Handles scheduling, client onboarding, and delivery tracking. Founder A covers the work now. Start the hire when the studio reaches 40 active clients.
- Finance Lead — vacant:Handles invoicing, bookkeeping, and cash reporting. Founder B covers the work now. Review the seat at the six-month mark and fill it if the finance workload is exceeding that coverage.
- Sales Lead — vacant:Qualifies leads and follows up on proposals. Both founders share the work now. At the six-month review, fill the seat if sales follow-up is displacing planned client work.
A vacancy with a trigger number is a plan. A vacancy without one is a wish.
The same constraint-first approach applies to operations plans examples.
Building the organization chart for a business plan
Checklist before drawing a single box:
Building the organization chart
- Every decision that moves money has one named owner.
- Every owner has a backup and a written backup rule.
- Every unfilled role appears as a dashed box.
- Every dashed box carries a number or a date.
Drawing comes last. Solid boxes for people, dashed boxes for vacancies, and one line under each dashed box explaining who covers the work now.
For this example, the solid boxes are the founders and the dashed boxes are vacant seats. Reporting lines show the roles’ coverage structure; the vacancy notes above name who performs the work until each seat is filled.
+------------------------------+ +----------------------------------+
| Founder A — Managing Partner |-----| Founder B — Finance & Growth |
+------------------------------+ | Partner |
| +----------------------------------+
- - - [Operations Lead — vacant] | \\
- - - [Finance Lead — vacant]
- - - [Sales Lead — vacant]
Founder A currently covers operations, Founder B covers finance, and both founders cover sales.
Staff-record software can help organize information, but it cannot decide who has authority. When evaluating organization plan software, keep the focus on the planning task rather than treating a tool as a substitute for the founders' decisions.
Where the numbers and the paperwork come from
Registry filings create the entity, while company description software can move those facts between forms without verifying them. Check company-description claims against the underlying records before using them in the plan.
Operations software can supply real numbers for the plan, but none of them will name your constraint for you. That naming job stays with the founders.
Who decides what in a business plan
The question of who decides what in a business plan is settled by the table, not by the prose around it.
Lenders care about who can sign and what the money buys. The SBA 7(a) page describes use of proceeds as part of what a lender reviews, so a two-person plan should answer it in a row.
