11 Risks
Manage costs, procurement, quality, specialization, competition, data, people, and cash flow; accept the growth and margin tradeoffs of avoiding paid advertising and personal entry points.
Praxis’s main risks are that low costs and specialization do not hold, or that purchasing, service quality, or cash flow cannot sustain the business.
Risks guide where we put effort
We prioritize resource purchasing, supplier management, production costs, and specialist experience. Our judgment is that getting these foundations right enables a supply-side platform to grow; they require ongoing monitoring, investment, and expansion, not a one-time build.
Eight risks need active mitigation. We also accept costs that follow from choosing not to buy advertising, build a sales force, or compete for the personal entry point.
| Risk | Related chapters | Treatment | Trigger |
|---|---|---|---|
| Cost structure fails | 3, 7, 10 | Mitigate | Production costs stop falling as methods improve, or purchasing advantage disappears |
| Purchasing advantage does not last | 7, 8 | Mitigate | Contracts expire without renewal; purchasing depends on one channel |
| Supplier quality or reliability declines | 2, 7 | Mitigate | Quality monitoring shows a deviation |
| Specialization is the wrong bet | 6, 8 | Mitigate | Specialist agents are no better than general agents |
| A peer with similar costs enters | 6 | Mitigate | Peers offer specialization and collaboration at lower prices |
| Data use is noncompliant | 7, 8 | Mitigate | Agreed purposes differ from actual use |
| Key people become overloaded | 10 | Mitigate | Critical judgment remains concentrated in one person |
| Cash flow comes under pressure | 12 | Mitigate | The timing gap between supplier payments and customer receipts widens |
| Slower acquisition, thin early profit, and forgone personal entry point and general-assistant opportunities | 7, 9 | Accept | Costs of the choice itself; no separate trigger |
Cost structure fails
Chapters 3, 7, and 10 share a premise: AI working methods and purchasing advantages support thin margins and no early platform fee.
The trigger is production costs no longer falling as methods improve, or the purchasing advantage disappearing.
The response is continuing improvement rather than a one-time cost cut; if either premise fails, charging platform fees earlier remains an option. This is the exception to waiting for scale under normal conditions.
Purchasing advantage does not last
Current terms in the business model and moat depend on time-limited contracts and relationships.
The trigger is an expired contract not being renewed, or purchasing continuing to rely on one channel.
The response is to keep adding channels and gradually move from relationship-based terms to terms supported by purchasing volume.
Supplier quality or reliability declines
The solution and business model require the platform to manage suppliers for customers and take responsibility for quality.
The trigger is a deviation in quality probes: programs that regularly check latency, error rates, and whether output meets expectations.
The response is ongoing monitoring, prompt supplier replacement, and proactive compensation rather than waiting for complaints.
Specialization is the wrong bet
Competition and the moat assume that focusing on a field and accumulating experience improve service.
The trigger is specialist agents being no better than general agents, with no continuing accumulation of industry working methods.
If this judgment fails, resource services and the complete process from building to operation still have value, but domain experience provides less protection.
A peer with similar costs enters
Companies such as Manus, discussed in Competition, may have production costs close to ours.
The trigger is a move into specialization and collaboration at lower prices; we cannot assume we will win on price.
The response is to rely on accumulated industry experience and proactive compensation commitments rather than continuing to compete on price alone.
Data use is noncompliant
The value of data in the business model and moat depends on compliance and agreed purposes.
The trigger is a difference between stated purposes and actual use.
The response is clear disclosure and customer choice. Our tradeoff is that customers whose strong privacy requirements do not fit this public cloud service are not suitable customers for it; compliance is a condition for data to be an asset, not an expense to omit.
Key people become overloaded
The team’s method still relies on human judgment, which can easily concentrate in a few people in a small team.
The trigger is critical judgment remaining concentrated in one person.
The response is to put repeatable decisions into rules and verification processes, keeping people’s workloads sustainable rather than depending on exhaustion.
Cash flow comes under pressure
The financial arrangements must manage the timing difference between customer prepayments and supplier payments.
The trigger is a widening gap that increases funding pressure.
Once the business holds funds in transit, it should manage them under applicable financial rules, set risk limits, and avoid putting those funds into positions that expose them to additional losses.
Costs we choose to accept
Without advertising or a sales force, customer growth may be slower than that of heavily funded competitors, and the brand must build through recommendations. Passing savings on means thin early profit; not competing for personal users or building a general assistant also means forgoing those opportunities.
Once core services and operating processes work well and the team has capacity, we can give acquisition more attention and investment. The focus here is business customer growth; serving businesses in their own operations remains our direction.
The next chapter turns these choices into near-term delivery and uses of funds.
10 Team & method
A founder leads an AI team, with collaborators and advisers. Engineering, open-source product, and business experience inform decisions; repeatable work and corrections become processes.
12 Milestones & financials
Complete four services, independent onboarding, three App surfaces, and the agent service lifecycle by the end of 2026. Funding supports leadership, building, procurement, compute, and channels.