Chapter 24: The Million-Dollar Solo Company

Turn a large economic ambition into explicit assumptions, a workable operating design, and a ninety-day sequence of evidence-producing decisions while preserving human judgment and the freedom to change direction.

A direction large enough to expose the assumptions

Audy’s first paid pilot has not produced a million-dollar company. In the fictional case, one educator agreed to an illustrative USD 300 engagement and accepted a repaired pack for rehearsal. The pack’s initial agenda exceeded the agreed thirty minutes; the repair preserved the participant attempt and revision while reducing the total. There is still no observed learner outcome or payment receipt.

That is a more useful place to end this book than an invented leap from one purchase to extraordinary wealth. Audy now has something specific to examine: a buyer situation, a deliverable, a correction, a record of the work involved, and an economic model whose assumptions she can challenge. The remaining distance is visible.

The million-dollar question gives that distance a scale. What would have to be true for one person to direct an operation earning a million dollars in annual revenue? Which constraints could change through better design? Which require demand, expertise, cooperation, or capital that has not been established? Which costs would a flattering answer leave out?

The Future Is Solo proposes that individual judgment, supported by systems, can direct work at a scale previously associated with larger organizations. We have treated that as a thesis to investigate through practice. Neither its ambition nor the machinery built around it establishes the viability of a particular enterprise. (The Future Is Solo, n.d.-b)

Your final artifact is a solo-enterprise plan. It connects a chosen economic direction with the evidence, operating limits, and next decisions needed to pursue it. The plan can lead to a smaller profitable service, an educational product, software, collaboration, or a decision to stop. It should make those choices more informed.

Name the million before calculating it

“A million-dollar company” can refer to several different things. This chapter’s main scenario uses USD 1 million in gross annual revenue: sales earned over a year before business expenses are deducted. That is the target being divided by a unit price. It is not a statement about the owner’s bank balance.

Profit requires attention to the costs included in the calculation. Chapter 22’s economics model separates a cash remainder before owner compensation and tax from an economic contribution that also values owner time. Both can be useful, provided their labels remain attached. A business can appear attractive when the owner works without an allowance and unattractive once that effort is included.

Owner income is what the owner receives under the business’s actual arrangements. It is constrained by costs, obligations, retained cash, and other claims on the operation. Revenue arriving in the business does not make the same amount available for personal use. An agreed fee is also different from an amount collected, as the pilot record already shows.

Valuation is a judgment about what ownership of the business is worth. It is not the annual sales figure renamed. A valuation claim would require its own assumptions and basis; this book does not supply a market multiple that turns Audy’s pilot into a priced company. Nor does a hypothetical valuation pay the expenses of the next delivery.

Choose the meaning relevant to your purpose, state the currency and period, and keep the others separate. If you want a sustainable owner income, a gross-revenue target alone is an incomplete guide. If you want to build an asset that can continue through a change of operator, its transferable procedures and dependencies matter alongside its sales.

Start with the economics that the pilot actually suggests

The illustrative baseline allocates four hours to delivery, including repair, two hours to acquisition across the three discovery conversations and two proposals, and one hour to support. The total is seven owner hours for the USD 300 agreed pilot fee. Cash cost is USD 20. Using USD 50 per hour as an assumed value of owner time gives USD 350 of time cost.

If the model treats the USD 300 as earned revenue, the unit’s economic contribution is negative USD 70: 300 minus 20 minus 350. It tells Audy that the offer needs investigation before she relies on repeated identical sales to support her work.

The monthly baseline makes the operating burden clearer. Assume 160 owner hours are available, with forty reserved for fixed operating work. That leaves 120 for units. At seven hours each, seventeen whole units fit, using 119 unit hours and 159 hours overall. Selling and earning all seventeen would produce USD 5,100 in revenue.

After USD 340 of unit cash costs and USD 200 of fixed monthly cash costs, the remainder before owner compensation and tax is USD 4,560. Valuing all 159 owner hours at USD 50 creates a USD 7,950 owner-time allowance. The resulting economic contribution is negative USD 3,390. The filled calendar has amplified the baseline problem.

As in Chapter 22, these monthly cash remainders assume all modeled revenue is collected and the listed cash costs are paid in the same period; no collection is observed in the pilot.

No part of that calculation establishes that seventeen buyers exist or that their work fits the same time allowance. It shows what the stated assumptions imply. The next useful question is which assumption Audy can responsibly change and test, rather than how to make the projection’s final cell look more encouraging.

Inspect the proposed improvement as a proposal

Chapter 22 considers an alternative at USD 750 per unit, USD 35 of unit cash cost, and six owner hours: three for delivery, two for acquisition, and one for support. The same 120 hours available for unit work would allow twenty units, using all 160 owner hours once fixed operating work is included.

If all twenty units sold and their revenue were earned under those assumptions, monthly revenue would be USD 15,000. Subtracting USD 700 of unit cash costs and USD 200 of fixed cash costs leaves USD 14,100 before owner compensation and tax. A USD 8,000 allowance for 160 owner hours leaves USD 6,100 of economic contribution in the model.

This is a different commercial proposition with unverified requirements. The price must be acceptable to relevant buyers. The three-hour delivery allowance must still produce the agreed result. Acquisition and support must remain within the stated amounts when the actual mix of buyers and problems appears.

The useful improvement is that the model now tells Audy what to investigate. She can examine which part of delivery might be narrowed or reused, how a buyer would understand the revised scope, and what could increase support. A failed test then identifies an assumption to change rather than leaving “the business model” as one mysterious object.

Keep the baseline beside the proposal. If a later experiment supports one changed assumption but not another, record that uneven result. A buyer might accept the higher fee while delivery still takes four hours. A redesigned pack might be faster to produce while too few people want it. Those outcomes imply different next moves.

Follow the arithmetic to the actual capacity gap

Twenty units per month at USD 750, repeated across twelve identical fully sold months, annualizes to USD 180,000. That is a conditional calculation. It assumes the same price, completed sales, work requirement, and available capacity throughout the year. It is not a forecast, a pipeline, or revenue the case has achieved.

At the same USD 750 price, gross annual revenue of at least USD 1 million would require 1,334 whole units. Those units would produce USD 1,000,500. The proposed capacity is only 240 units across twelve months. The gap remains even if every available slot sells.

Under the unchanged six-hour unit assumption, 1,334 units would require 8,004 owner hours for unit work alone, before fixed operations. That is incompatible with the model’s 160-hour monthly allocation. More enthusiastic marketing cannot fit those hours into the same operating design. More drafting agents cannot make the customer-facing judgment and support disappear by definition.

A different design might change the relationship between a sale and owner work. A reusable resource may require less direct delivery for each buyer. A group format may serve several participants in one supported session. A higher-value service may support a different price. Software may automate a stable operation. Each possibility changes the proposition and introduces its own assumptions.

The arithmetic should therefore end one line of reasoning: Audy cannot reach the chosen annual target merely by repeating the proposed pilot unit within the current time budget. It begins another: which useful product and operating arrangement could alter that constraint while preserving quality, demand, and a life she wants to lead?

Leave room before promising the modeled ceiling

The proposed twenty-unit month uses all 120 hours allocated to units and all forty hours assigned to fixed operations. The model contains no additional owner-time reserve beyond those categories. If a delivery overruns, support increases, or an interruption removes available hours, the same monthly promise no longer fits without something else changing.

Audy can choose to commit below the calculated maximum while learning how much variation the work contains. The enterprise plan should name that operating choice and show its effect on revenue and compensation. A reserve is a use of capacity, so it must remain visible rather than being counted simultaneously as free time and sold work.

Cash has a related timing problem. A fee can be agreed before cash arrives, while some costs are paid earlier. The pilot supplies no collection record, so the model cannot establish the money available to fund another engagement. For actual work, retain the payment status and the timing of known obligations beside the revenue calculation. A profitable-looking period can still contain a point at which the planned payment is not available.

Choose what you are willing to commit before adding the next task. This can include owner hours, cash, the number of simultaneous engagements, and the kinds of promise the current evidence supports. Revisit these limits when actual work shows that the assumptions are too narrow or unnecessarily restrictive.

The same discipline applies to continuity. If a service depends on your review, decide what happens when you cannot provide it. A waiting state, an agreed later date, or a qualified collaborator may be more credible than an automatic substitution that has never been tested. Describe that dependency before selling an expectation the operation cannot meet.

The ninety-day exercise can reveal the appropriate margin for your situation. Keep the expected work, actual work, and changes in availability separate, then inspect what forced a reschedule or repair. You are learning how the enterprise behaves under ordinary variation. A plan that works only when every unit and every week match the neatest example should remain an experiment rather than a dependable commitment.

Decide which constraint deserves the next experiment

Capacity is only one possible constraint. An operation may have unused delivery time because few relevant buyers know about it. It may attract interest but lose buyers when the scope is explained. It may sell well and require so much repair that every extra engagement consumes the reserve. Treat those conditions differently.

For Audy, the evidence is still too small to name a permanent bottleneck. One fictional pilot exposes a duration-review defect and a demanding unit model. It does not establish a reliable acquisition process, a market-wide price ceiling, or a stable delivery time. Her next experiment should narrow one of those uncertainties.

Write the assumption in language that can be checked. “Distribution will improve” is vague. “This specific type of educator has a current brief, recognizes the defined problem, and is willing to consider the stated offer through this permitted contact route” identifies something to investigate. A recipient count alone would not establish the rest.

Likewise, “AI will reduce delivery work” should become a particular proposed change. Perhaps a reusable source-linked example removes repeated formatting. Perhaps the review still needs the same attention because each brief has different learning constraints. Record what changes and compare the whole delivery, including correction, before counting a saving.

Choose the constraint that blocks the next useful commitment. If you cannot reliably deliver the existing scope, taking on more work is premature. If the delivery is sound but demand remains unknown, another infrastructure project may avoid the relevant question. The enterprise plan should make that trade-off explicit.

A service can grow by narrowing and deepening

A service route keeps human judgment close to the buyer’s particular situation. Audy might learn to distinguish a quick brief review from a deeper activity redesign, with different inputs and delivery boundaries. That could make the work easier to explain and estimate. It would need buyer and delivery evidence before becoming a dependable offer.

Higher prices would require a credible useful difference for the chosen buyer. A shorter turnaround, clearer decision, or work supporting a more consequential event might matter in a particular context. Those are hypotheses, not permissions to rename the same uncertain service “premium” and treat the price increase as earned.

Standardization can remove repeated work when the repeated part is truly shared. A reusable review sheet, intake format, or source-reference convention may help while leaving the actual design judgment specific to the brief. The cost model must retain whatever review and support remain. A template is valuable when it performs useful work, not when it hides the work someone still has to do.

The service route can also lead to a deliberately smaller enterprise. A manageable number of well-scoped engagements, adequate compensation, and protected time may serve the owner’s purposes better than the largest available revenue target. Choosing that arrangement after inspecting the evidence is an exercise of agency.

An educational product changes the delivery question

An educational resource could let an educator use the accumulated examples, criteria, and facilitation guidance without commissioning a full redesign. A group program could combine reusable material with bounded human feedback. Both forms alter how many people may benefit from one piece of preparation, while creating questions about use, support, and continued quality.

The next test should examine the part that direct service previously supplied. Can the intended user locate the appropriate activity, understand the criteria, and adapt the material within its stated scope? Where do they need an explanation that is still trapped in Audy’s head? An attractive download does not answer those questions.

Separate the purchaser from the learner when their roles differ. An educator may buy a facilitator pack, while participants later perform the exercise. Purchase, educator satisfaction, successful facilitation, and learner performance are different evidence. Decide which claim the next test is meant to support and retain the appropriate authorized observation.

Do not assume that a digital format removes marginal work. Questions, corrections, accessibility needs, updates, and delivery arrangements can still consume attention or cash. A reusable product changes the pattern of work; its economics need to show where that work went. Test a small version whose dependencies you can inspect before promising support at a scale you have never handled.

Software changes what must be maintained

A software route becomes interesting when a valuable operation has sufficiently clear inputs, behavior, and review requirements. The action-list practice offers a narrow starting point, but a tool serving real users would need more than a successful synthetic table. Its source handling, permission boundaries, output presentation, error reporting, and recovery would become part of the product.

Begin by showing how the proposed interaction helps someone complete a task. A manually delivered prototype can test parts of that experience if it is honestly described. Later, automate the stable operation and inspect the behavior it actually produces. A working interface can still hide a process that requires extensive human rescue.

Software can introduce costs that a delivery-only model omits: ongoing maintenance, hosting, monitoring, user support, and handling failures. Put the costs and owner time relevant to your actual design into the model, and mark estimates separately from observed bills and work.

The choice of more agents should follow the operation. Distinct roles may help divide evidence gathering, drafting, and checking. They also require correct joins, bounded authority, and review of the resulting state. An additional agent is not an additional buyer, and parallel generation is not evidence that the end-to-end service needs less supervision.

Read the real experiments without inventing their ending

The TFIS build deck provides a useful counterpart to Audy’s constructed case. Its Kosong entry describes a command-line experiment connected to SovMem, open-source distribution, and GitHub Actions runners. Monetization appears as the next question. That distinction is useful: distributing a tool and discovering a sustainable exchange are separate pieces of work. (The Future Is Solo, 2026, slide 39)

The AI Fluency go-live entry names work on asset access, delivery, payment-related integration, and email access, then places distribution next. (The Future Is Solo, 2026, slide 40) Another entry describes an AI Ethics in Education course MVP and lists conversion to a paid online course as further work. (The Future Is Solo, 2026, slide 44) These are reported development notes, not independent proof of sales, completed monetization, or learner effectiveness.

The pattern matters more than a triumphant ending added by a narrator. A build creates a new possibility and exposes another question. Distribution does not follow automatically from deployment; buying does not follow automatically from attention; educational value does not follow automatically from a payment integration. The next experiment has to address the particular missing relationship.

Your records can preserve the same discipline. Write what was built, which behavior was inspected, what a user actually did, and what remains next. Do not move a task from the last category to the first merely because the story would read more smoothly with everything completed.

Use the first thirty days to establish a trustworthy baseline

The ninety-day plan begins from the present evidence, not from a promised revenue curve. In the first month, choose one offer and a small working scope. Review the pilot record, identify the recurring delivery steps, and keep the acquisition and support work visible. Check whether the assumed cost categories describe the work you would actually have to perform.

For Audy, the existing seven-hour pilot record is illustrative. A real reader should replace those values with their own observations from authorized work or a clearly labeled rehearsal. Record interruptions and repair, not only the time the assistant generates text. Distinguish work done once to prepare the service from work expected with each buyer, and keep uncertain classifications open for review.

Use discovery to examine the current buyer situation. Obtain appropriate agreement to discuss the work and retain notes. Inspect a relevant brief where permitted. Preserve differences among accounts instead of translating every response into support for the same offer. Keep the number of outreach or proposal attempts bounded by the review and delivery capacity you can actually provide.

By the end of the first month, the useful output is a revised experiment record and a source-based cost model. Continue only with an offer whose input, output, acceptance, scope, and effort can be explained. If those remain unclear, narrow the task or return to the relevant capability practice. More commitments would obscure the gap rather than repair it.

Use the middle thirty days to test a specific redesign

The second month investigates one proposed change to the operating design. Audy’s candidate might be a narrower pack whose reusable material reduces repeated delivery work. A different reader might test a group format, a resource used without live explanation, or a more valuable service scope. State the expected useful change and the observation that would challenge it.

The USD 750 proposal is available as a modeling scenario, not a price already validated by the case. If you test a different scope and price, describe them clearly to the buyer and record the actual response. A willingness to discuss it remains different from an agreement. A refusal can reveal timing, fit, or value concerns without establishing one universal reason for every buyer.

Inspect delivery under the revised arrangement. Keep the first candidate, review, repair, and total work. If the proposal assumes three delivery hours but actual work needs five, preserve five. If reducing the work also removes an essential participant attempt or source review, the apparent efficiency has changed the product’s quality standard.

At the end of this period, compare the supported assumptions with the original model. Continue, revise, or stop the particular redesign. Do not silently change the target halfway through and then report that the original prediction succeeded. The record should show what changed your decision, including when the answer is that a smaller improvement is all the evidence supports.

Use the final thirty days to decide what deserves repetition

The third month asks whether the useful parts can be repeated and recovered under the conditions you intend to rely on. Review comparable deliveries or rehearsals, including the failures and support they required. A single unusually easy engagement should not define the operating allowance for a more varied service.

Check the dependencies that expansion would make consequential. Can the current procedure be reconstructed from the maintained records? Does a missing source create the right hold? Can you identify the reviewed candidate and distinguish it from a stale one? If another provider or collaborator will be relied on, perform the relevant authorized handoff rather than assuming equivalence.

Use the evidence to choose the next commitment. You might repeat a narrowly supported offer, revise price or scope, keep delivery manual, add a specific collaborator, or stop an unpromising route. A plan that allows only expansion cannot respond honestly to what the experiment discovers.

The final document should state the offer you will continue, the capacity you can defend, the costs still estimated, the cash and time you will not commit beyond their limits, and the next condition requiring review. The ninety days do not need to end with a million-dollar forecast. They should end with a more dependable basis for your next decision.

Decide what solo should mean in your enterprise

Solo can describe who owns and directs the operation without implying that the person has no relationships, outside services, or expert help. Your plan should state what you mean by the term. If the target requires contractors, partners, or employees, include their work, cost, authority, and coordination rather than leaving them invisible to preserve the label.

Choosing a team can be a sensible response to the work. A task may need expertise you should not improvise, human availability you cannot provide, or collaboration that improves the product. The TFIS thesis can prompt a serious investigation of what one person can direct; it need not become an obligation to reject help that serves the actual purpose.

Equally, keeping a smaller operation can be a deliberate design choice. You may prefer a bounded service, a modest product, and enough time to learn and maintain it well. The capability to build larger systems remains useful even when you choose not to maximize their throughput.

Make owner attention part of the plan. Name what deserves your judgment, what can proceed under established rules, and what must stop when you are unavailable. A business that uses every free hour to keep its machinery functioning has consumed a resource that the revenue target alone cannot describe.

Keep curiosity available after the calendar fills

The Functional Life includes exploratory play among its operating practices. Applied to this enterprise, that means retaining some room to investigate questions that are not simply the next delivery task. Such time needs a place in the operating design; it will not reliably appear because an automation was supposed to save it. (The Future Is Solo, n.d.-a)

Curiosity also remains useful when it questions the business you have already built. A recurring support problem may reveal a misunderstood user need. A tool failure may show that a dependency should remain manual. A buyer’s refusal may reveal an assumption that polished product language had concealed. Protect the ability to hear those signals without defending every earlier choice.

TFIS’s article The Meaning of Life: A Techno-Optimist’s Response presents meaning as something developed through building, failure, and learning. Its visible attribution describes an article in Khalil Nooh’s voice. We can engage with that stated philosophy without turning its ambitious business question into an achieved result or inventing autobiography on the author’s behalf. (The Future Is Solo, n.d.-c)

You can take a practical question from it: is the work worth the time and attention you are giving it? Revenue is relevant to that answer because an enterprise must support its obligations. It is not the only measure of whether the activity is useful, understood, or chosen with care.

Leave with a plan you can challenge

Complete the solo-enterprise plan. Name the economic target precisely, copy the current evidence rather than the hoped-for ending, and show the assumptions that connect price, demand, capacity, cost, and owner work. Choose one operating route and the next experiment it requires. Keep alternatives available where the evidence has not settled the choice.

Write the stop and change conditions before the next commitment. If actual delivery exceeds the available window, stop adding work and repair the scope or capacity plan. If source review cannot support the promised output, hold the affected delivery. If buyers do not choose the specific offer, return to the relevant problem or proposition instead of reporting interest as sales.

Explain the plan without AI. Show why a million in annual sales is different from owner income or valuation. Show where the proposed twenty-unit month gets its demand and time assumptions. Name the evidence you would need before depending on them. A plan that you cannot explain should not acquire authority because an assistant has formatted it convincingly.

Mind gave you a way to ask a useful question, investigate it, and explain what you understand. Memory made the supporting evidence, decisions, and corrections recoverable. System turned those materials into operations you could inspect, delegate within limits, and test against an exchange with someone else. The arcs meet in your ability to create value while knowing what the result does and does not establish.

Audy’s next step remains a bounded experiment. Yours can be equally concrete: one useful task, one claim to test, one piece of work someone can inspect, and one decision changed by what you learn. The company may grow. The offer may change. What accumulates is the capability to make those choices with understanding, and to build something worth continuing.

References

The Future Is Solo. (n.d.-a). The functional life (Field Manual No. 01). Retrieved September 10, 2026, from https://life.thefutureissolo.com/

The Future Is Solo. (n.d.-b). The future is solo. Retrieved September 10, 2026, from https://thefutureissolo.com/

The Future Is Solo. (n.d.-c). The meaning of life: A techno-optimist’s response. Retrieved September 10, 2026, from https://witmol.thefutureissolo.com/

The Future Is Solo. (2026). The Future Is Solo 20260910 [Google Slides presentation]. https://docs.google.com/presentation/d/1dvbBGs22QvtGogevZ6f5mf8YQE7WDAPBwYlclhTyctI/edit