Start focused. Scale with evidence.
ReddyStack offers three engagement shapes: a focused Proof Sprint, a connected Stack Build, and ongoing Operate and Improve support. The right starting point depends on the decision you need to make, the current evidence, and how much implementation is required.
Every quote names the problem, baseline, deliverables, access, approvals, revisions, exclusions, separate costs, evidence plan, and handover. Prices come after the scope is understood; no package hides media spend, platform costs, or client responsibilities.
Proof Sprint
Solve or test one clear growth problem, then review the evidence together.
- One problem, one decision
- Baseline recorded first
- Evidence summary at the end
Stack Build
Build the connected pieces your plan needs: site, search, ads, creative or tracking.
- Several layers, one plan
- Defined deliverables
- Clean handover of accounts
Operate & Improve
Review results on a set rhythm and improve what's working.
- Agreed priorities
- Regular reporting
- Tests, not guesses
A common Proof Sprint: the Google Ads & PPC audit, which checks tracking, search terms and settings before any budget changes.
| Engagement | Fits when you have | What you get | Shape |
|---|---|---|---|
| Proof Sprint | One important unknown or bottleneck. | A focused audit, build, fix or test, plus the evidence and its limits. | Bounded project |
| Stack Build | A defined implementation that needs several connected capabilities. | The connected pieces your plan needs, with a clean handover of accounts. | Bounded project |
| Operate & Improve | A working system that needs ongoing testing and decisions. | Agreed priorities, regular reporting and review periods. | Ongoing |
Written down before work starts.
- The problem
- The baseline
- Deliverables
- Access
- Approvals
- Revisions
- Exclusions
- Separate costs
- Evidence plan
- Handover
Costs that stay in your name.
- Advertising spendNot in fees
- Hosting & domainsNot in fees
- Paid toolsNot in fees
- Stock assetsNot in fees
- AI model usageNot in fees
- Other third-party costsNot in fees
Unless the proposal explicitly says otherwise. You approve spending boundaries before anything launches.
Which engagement should I start with?
Start with the problem, not the package. A Proof Sprint fits one important unknown or bottleneck. A Stack Build fits a defined implementation that needs several connected capabilities. Operate and Improve fits a working system that needs ongoing testing and decisions. Rahul recommends the smallest engagement that can still produce a useful result.
What does a Proof Sprint include?
The sprint defines one decision, establishes the current baseline, completes a focused audit, build, fix, or test, and records the evidence and limitations. Its output depends on the problem and can include a landing path, search repair, tracking check, campaign test, creative comparison, or workflow prototype. It is bounded work, not an unlimited trial retainer.
Are media spend and platform costs included?
No unless the proposal explicitly states otherwise. Advertising spend, hosting, domains, paid tools, stock, model usage, and other third-party costs remain visible and separate from ReddyStack fees. The client keeps ownership of the relevant accounts and approves spending boundaries before launch.
Is the work one-off or ongoing?
A Proof Sprint and Stack Build can be bounded projects. Operate and Improve is ongoing work with agreed priorities, reporting, and review periods. A completed project does not silently include indefinite monitoring, optimisation, new assets, or support; the proposal states what continues and what ends at handover.
What happens when the brief changes?
First compare the request with the approved scope. A correction or refinement inside the agreed direction differs from a new page, workflow, language or creative concept. If the request adds work, discuss the revised deliverables, price and timing before proceeding. Revision rounds, approval contacts and exclusions belong in the original proposal so there is a shared reference.
Can we start with a smaller budget?
A smaller first phase can work when it still completes a useful task. For example, one well-defined service page may be a better starting point than several unfinished pages. Share the actual budget and identify what can wait. A revised scope should remove named optional work while retaining the checks needed for the agreed deliverable to function.
A short call to understand the goal, look at your current setup and agree whether a Proof Sprint makes sense.