Full-Stack Company
Source-grounded pack with Build Buy Partner Brief, Control Point Map, and Integration Boundary Audit, plus 3 more.
Get this packGrounded in the complete Full-Stack Company series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 6 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches Full-Stack Company and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
6 source-grounded skills. Load one workflow at a time.
Build Buy Partner Brief
Use this workflow when a specific workflow, infrastructure, service, distribution, compliance, data, or trust layer could be owned, bought, partnered, outsourced, automated later, or left alone and leadership needs a decision grounded in learning, outcomes, access, economics, capability, maintenance, dependency, and reversibility.
Output specification
Return a build-buy-partner decision brief with layer_and_outcome, strategic_trigger, options, learning_and_control, economics, capability_fit, maintenance_tail, risk, recommendation, and switch_trigger.
Control Point Map
Use this workflow when an AI company must determine which workflow layers create defensible access, context, judgment, traces, feedback, trust, or economic control and needs to distinguish strategically valuable workflow ownership from point automation or integration theater.
Output specification
Return a workflow control-point map with customer_outcome, workflow, traces, control_points, dependency_leaks, scores, ownership_mechanisms, and test.
Integration Boundary Audit
Use this workflow when leadership needs a company, business-unit, or product-line audit of what to own, buy, partner, outsource, automate later, or leave alone across outcomes, workflows, data loops, services, distribution, trust, economics, capability, and explicit non-integration decisions.
Output specification
Return a full-stack boundary audit with scores_and_evidence, disagreements, layer_decisions, non_integration_rationale, binding_constraint, 90_day_actions, deliberate_deferral, and review.
Outcome Stack Economics
Use this workflow when a company wants to sell a managed or measurable outcome rather than software enablement and must test workflow control, customer dependencies, service and review burden, quality risk, pricing readiness, capital and labor needs, utilization, cost-to-serve, and margin direction by cohort.
Output specification
Return an outcome-stack economic model with promise, workflow_control, customer_dependencies, quality_and_risk_controls, cost_structure, cohort_scenarios, conversion_path, pricing, and proof_gates.
Proprietary Data Loop
Use this workflow when a company claims proprietary data but has static, stale, unlabeled, permission-constrained, or outcome-disconnected records and needs to instrument a strategic workflow so context, AI recommendations, human judgment, corrections, outcomes, permissions, and improvement form a live loop.
Output specification
Return a proprietary data-loop design with target_decision, context, system_output, human_judgment, outcome, trace_quality, permissions, owners, feedback_actions, and health_rating.
Vertical Integration Roadmap
Use this workflow when a company has evidence that distribution, services, implementation, trust, compliance, brand, or another business layer could improve workflow learning, customer access, outcome delivery, or defensibility and needs a sequenced capability and productization roadmap.
Output specification
Return a vertical integration roadmap with layer_mechanisms, distribution_control, services_conversion, trust_stack, capability_build, sequence, milestones, partner_learning_rights, and exit_conditions.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.