Decide whether to build a capability, buy a tool, or partner for it — total cost honesty, strategic-control weighting, and the reversibility of each path.
Decide: build, buy, or partner for {{capability}}. Context: {{context}} (why we need it, how core it is to how we win, our team's capacity, options I know of).
Analyse: the strategic test first (is this capability part of how we WIN, or just something we need? core → bias build/control; context → bias buy), total cost honesty per path (build: the maintenance forever, not just the build; buy: per-seat creep, integration, lock-in; partner: revenue share and dependency), speed-to-value per path, reversibility (which paths can we back out of — weight the reversible ones when uncertain), and the capacity reality (build competes with my roadmap — what specifically wouldn't ship). Verdict with the conditions that would flip it, and the contract/architecture clause per path that preserves the exit.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekRun the mid-quarter OKR check: score trajectories honestly, decide push/pivot/drop per key result, a...
Turn abstract company values into observable behaviours: the do/don't pairs, the hiring and review h...
Screen a potential business acquisition before falling in love: the strategic fit, the red-flag scan...
Run a SWOT analysis that ends in strategy, not a four-box poster: evidence-backed entries, cross-qua...
Compress your strategy onto one page: the diagnosis, the guiding policy, coherent actions, and what...
Write OKRs that pass the tests most fail: outcome objectives, measurable key results that aren't tas...