Zum Hauptinhalt springen
Scale Your Product/Service
ScalingBusiness GrowthOperationsBottleneck AnalysisPrompt Engineering

Scale Your Product/Service

T. Krause

Growth and scale are not the same thing. This prompt produces a scaling roadmap that identifies your real constraints — and grows revenue without growing chaos at the same rate.

Scaling a business is where many good companies break. A product or service that works beautifully at small volume develops cracks as it grows: the founder becomes a bottleneck, quality slips, costs rise as fast as revenue, and the operation that felt agile becomes fragile. The instinct is to push harder on sales — but pouring more demand into a constrained system does not scale it. It strains it.

This prompt produces a scaling roadmap built around a simple principle: scaling is the work of finding what currently limits your capacity and systematically removing it. It diagnoses where your business will break first, sequences the changes that raise your real ceiling, and distinguishes the moves that create durable scale from the ones that just create more work.

What It Does

  • Diagnoses the specific constraints — people, processes, systems, or founder dependency — that limit the business's current capacity.
  • Produces a sequenced scaling roadmap that raises capacity ahead of demand rather than behind it.
  • Distinguishes investments that create leverage from activity that simply adds volume and cost.

The Prompt

#CONTEXT:
I run a business that is working at its current size, and I want to scale it — meaning grow revenue and output substantially without a proportional increase in chaos, cost, or founder workload. Your job is to help me build a scaling roadmap grounded in my actual constraints. Scaling is not the same as selling more; it is raising the business's capacity to deliver. Help me find what would break first if demand doubled, and design the sequence of changes that would raise that ceiling.

#ROLE:
You are an operations and growth strategist who has helped service businesses and product companies move from founder-dependent operations to scalable systems. You think in terms of bottlenecks, unit economics, and leverage. You are direct about the difference between activity that scales and activity that merely accumulates.

#RESPONSE GUIDELINES:
1. Begin by mapping how the business currently delivers value, end to end, and identifying where the founder or a key person is a single point of failure.
2. Identify the constraint that would break first if demand doubled — people capacity, process, systems, cash, quality control, or supply.
3. Assess unit economics: does each additional sale currently make the business stronger or just busier?
4. Produce a sequenced roadmap that removes constraints in order, raising capacity before demand is added.
5. For each step, distinguish whether it creates leverage (a fixed effort that serves growing volume) or linear cost (effort that grows with volume).
6. Flag the risks of scaling prematurely — the things that should be fixed before growth is accelerated.

#SCALING QUALITY CRITERIA:
1. Constraint-focused: The roadmap targets the actual bottleneck, not the most visible symptom.
2. Sequenced: Capacity-building steps come before demand-generating steps.
3. Leverage-aware: Each recommendation is classified as leverage-creating or linear-cost.
4. Economics-grounded: The plan only encourages scaling activity where unit economics are healthy.
5. De-risked: Premature-scaling risks are named with conditions that must be met first.

#INFORMATION ABOUT ME:
- What my business sells and how it delivers it: [BUSINESS_AND_DELIVERY_MODEL]
- Current size — revenue, customers, team: [CURRENT_SIZE]
- My growth goal and timeframe: [GROWTH_GOAL_AND_TIMEFRAME]
- Where I already feel strain or bottlenecks: [KNOWN_PAIN_POINTS]
- My role in daily delivery today: [FOUNDER_INVOLVEMENT]

#RESPONSE FORMAT:

Value Delivery Map:
[How the business currently delivers, end to end, with single points of failure marked]

Primary Constraint:
[What breaks first if demand doubles, and why]

Unit Economics Assessment:
[Whether each additional sale strengthens or strains the business]

Scaling Roadmap:
Step 1 — [Name]:
- Constraint addressed: [Which]
- Action: [Specific change]
- Type: [Leverage-creating / linear-cost]
- Sequencing note: [Why this comes now]

Step 2 — [Name]:
[Same structure]

Step 3 — [Name]:
[Same structure]

Premature-Scaling Risks:
- [Risk]: [Condition that must be met before accelerating growth]

How to Use

  1. Describe your delivery model in detail — how a sale actually becomes a delivered product or service, and who touches it along the way.
  2. Be honest about where you already feel strain; the bottleneck is often hiding inside the part of the business you find most stressful.
  3. Copy the completed prompt into your preferred AI tool.
  4. Review whether the roadmap sequences capacity ahead of demand — if it recommends selling more before fixing delivery, push back.

Example Input

## Information about me

- What my business sells and how it delivers it: A web design agency; I personally scope every project, manage two contractors, and handle all client communication
- Current size — revenue, customers, team: €280k annual revenue, ~20 projects/year, me plus two freelance contractors
- My growth goal and timeframe: Reach €600k revenue within 24 months
- Where I already feel strain or bottlenecks: I am involved in every project, can't take on more than 2 projects at once, and projects stall when I'm unavailable
- My role in daily delivery today: I am the bottleneck — scoping, client management, and quality review all run through me

Tips

  • Find the constraint before you spend on growth. Marketing that drives demand into a constrained business creates unhappy customers, not scale. Fix the ceiling first.
  • Be brutally honest about founder dependency. If the business cannot deliver a sale without you personally, that is almost always the first constraint to remove.
  • Classify every initiative as leverage or linear. Hiring one more person to do more of the same work is linear. Building a system, process, or product that serves many customers at once is leverage. Favor leverage.
  • Re-run after each phase. Removing one constraint reveals the next. Treat the roadmap as a living document and re-run the prompt once the first bottleneck is cleared.
  • Pair it with a unit-economics check. Scaling a business with weak margins just scales the losses. Confirm the economics are healthy before accelerating.

We use cookies

We use cookies to ensure you get the best experience on our website. For more information on how we use cookies, please see our cookie policy.

By clicking "Accept", you agree to our use of cookies.
Learn more.