POST /v1/strategy/run
{
"entity_type": "solo_founder",
"source": "onboarding_intake",
"profile": {
"stage": "idea_validation",
"weekly_capacity_hours": 10,
"budget_range": "low",
"risk_tolerance": "medium",
"preferred_work_style": "deep solo work with light client contact"
},
"context": {
"declared_goal": "choose and validate a focused business direction",
"limits": [
"must keep full-time job",
"no paid ads yet",
"needs first revenue within 90 days"
],
"evidence": [
"sales call notes",
"survey answers",
"skill inventory",
"market research snippets"
],
"current_options": ["consulting", "digital product", "niche SaaS"],
"requested_outputs": [
"strategy_map",
"ranked_priorities",
"risk_register",
"kpi_snapshot",
"next_actions"
]
}
}For your software
The strategy engine, as an API.
The same engine behind our Personal and Founder products, exposed directly. Send goals, notes, limits, and progress data. Get back a structured strategy, every priority, risk, measure, and next action linked in one graph, as JSON with the same fields every run.
Raw context in. Structured strategy out.
200 OK
{
"run_id": "strat_9x42",
"strategy_map": {
"vision": "build a durable solo business around a high-fit problem",
"mission": "validate one narrow service offer before building assets",
"goals": [
{ "id": "G1", "name": "positioning", "status": "needs_focus" },
{ "id": "G2", "name": "sales_validation", "status": "priority" },
{ "id": "G3", "name": "delivery_system", "status": "later" }
],
"objectives": [
{ "id": "O1", "target": "10 qualified interviews", "due_in_days": 21 },
{ "id": "O2", "target": "one paid pilot", "due_in_days": 45 },
{ "id": "O3", "target": "repeatable delivery checklist", "due_in_days": 60 }
],
"tactics": [
"choose one customer segment",
"write the smallest paid offer",
"book five discovery calls this week",
"review progress every Friday"
]
},
"scores": {
"clarity": 0.84,
"fit_confidence": 0.78,
"execution_risk": 0.36,
"drift_watch": ["scope creep", "channel hopping", "overbuilding"]
},
"next_actions": [
{ "rank": 1, "action": "Pick one customer segment", "reason": "reduces positioning drift" },
{ "rank": 2, "action": "Draft the paid pilot", "reason": "tests willingness to pay" },
{ "rank": 3, "action": "Run weekly review", "reason": "keeps strategy tied to reality" }
]
}Why structured output
Free-form text is the expensive way to build.
The cost of a strategy feature is rarely the model call. It is the reasoning layer you build and the parsing code you maintain. Strategy API is designed around a stable output contract instead of loose prose.
Stable output contract
Responses use predictable fields your app can store, display, compare, and validate.
Clear schema design
Named fields for priorities, risks, measures, reasoning, and next actions reduce ambiguity for product teams.
Less parsing burden
A known output shape reduces the defensive parsing and copy cleanup normally required around free-form responses.
Reusable strategy layer
Intake, normalization, priority logic, and review fields live in one layer your product can call repeatedly.
Who it is for
The right call for some products, not all.
- You are putting strategy, prioritization, or onboarding logic into your own product.
- You need the same fields every run so your UI and database stay stable.
- You would rather buy the reasoning layer than build and maintain it.
- You want a clear pricing path that scales with real usage.
- You want Aimspace to build a finished system for you. Use Personal Strategy System or Founder Strategy System.
- You need a one-time personal or business strategy system, not an integration.
- You only need occasional free-form answers from a general chat model.
- You are not building software around the output.
The problem
Turning context into structure is the hard part.
Prose is hard to productize
A smart-sounding paragraph is still difficult to store, display, compare, or run inside a workflow. Your product needs fields, not essays.
Strategy logic is expensive
Useful strategy output needs intake logic, normalization, priorities, risks, measures, reasoning, and review fields. Building that from scratch is a project on its own.
Output has to stay consistent
Software needs stable contracts. When the model changes shape every run, the product experience breaks and your team debugs the difference.
The solution
A strategy layer your product can call.
Aimspace takes raw user or business context and returns structured strategy objects your product can display, store, automate, and compare over time.
The same intake logic
The API starts from goals, limits, evidence, current state, and the outputs you request, so it works from real context rather than a blank prompt.
The same output contract
Responses arrive as structured priorities, risks, measures, reasoning, and next actions your product can render or store directly.
The same review loop
The structure supports later runs that compare strategy, reality, drift, and updated priorities as the data set grows.
What you get
A strategy graph, plus the scores to trust it.
Every response is a connected strategy graph and a set of analysis metrics, so your product can both render the plan and judge its quality.
Strategy graph
Vision, mission, goals, objectives, and tactics as nodes, with typed edges showing what supports, depends on, or justifies what.
Priority logic
Ranked next moves with reasoning, limits, and confidence notes your app can surface directly.
Risk and drift
Known risks, assumptions, blockers, and where execution tends to drift from the plan.
Alignment scores
Confidence, root coherence, misalignment, drift, and collapse risk, so you can flag a weak or off-track plan automatically.
How it works
From raw user input to strategy objects.
The same Aimspace loop, adapted for builders who need stable, structured output inside their own software.
Send context
Pass goals, notes, limits, files, measures, history, or form answers into the endpoint.
Confirm use case
Review sample input and output to confirm the fields, workflow, and production use case before choosing a paid tier.
Generate structured strategy
One strategy run returns priorities, risks, measures, reasoning, next actions, and strategy-map logic.
Ship into product
Use the output inside your app, dashboard, agent workflow, client-facing report, or recurring review loop.
API access
Buy credits or choose a monthly plan.
Use prepaid credits for testing or occasional runs. Use a subscription when usage becomes regular. One strategy run = one full strategy generation from one context payload.
| Option | Price | Included strategy runs | After included runs | Get access |
|---|---|---|---|---|
| Small credits | $49 | 5 strategy runs | Buy more credits | Buy credits |
| Medium credits | $129 | 15 strategy runs | Buy more credits | Buy credits |
| Large credits | $199 | 25 strategy runs | Buy more credits | Buy credits |
| Starter | $149/mo | 100 strategy runs | $3/run | Subscribe |
| Growth | $699/mo | 1,000 strategy runs | $1.50/run | Subscribe |
| Platform | $2,999/mo | 5,000 strategy runs | $1/run | Subscribe |
| Custom | Contact | Custom volume | Custom | Contact |
Small credits
$49
Testing and occasional use
- Included strategy runs
- 5 strategy runs
- After included runs
- Buy more credits
Medium credits
$129
Small pilots
- Included strategy runs
- 15 strategy runs
- After included runs
- Buy more credits
Large credits
$199
Larger tests before subscribing
- Included strategy runs
- 25 strategy runs
- After included runs
- Buy more credits
Starter
$149/mo
First production integrations
- Included strategy runs
- 100 strategy runs
- After included runs
- $3/run
Growth
$699/mo
Growing apps and workflows
- Included strategy runs
- 1,000 strategy runs
- After included runs
- $1.50/run
Platform
$2,999/mo
High-volume platforms
- Included strategy runs
- 5,000 strategy runs
- After included runs
- $1/run
Custom
Contact
Enterprise volume and support
- Included strategy runs
- Custom volume
- After included runs
- Custom
FAQ
The questions builders ask first.
What does the API return?
Structured strategy output: priorities, risks, measures, next actions, strategy-map logic, and review-ready fields, all on a stable schema.
What is a strategy run?
One strategy run is one full strategy generation from one context payload. It can be used for onboarding, a dashboard, a report, or a recurring review flow.
Is this an LLM wrapper?
It is a strategy layer with a fixed output contract. Your product relies on consistent fields every run, so you build against data rather than free-form prose.
Who is this for?
Apps, workflow tools, internal agents, communities, and platforms that need strategy logic and would rather not build the modeling layer from scratch.
Can I review the output before paying?
Yes. The page includes sample input and output so you can see the shape before requesting production access.
Can I buy access today?
Yes. You can buy prepaid API credits with no subscription, or choose a monthly plan when usage is regular.
Strategy API
Build with structured strategy output.
Buy prepaid credits to test the API, or choose a monthly plan when usage is regular.
Buy API credits →