Skip to content

My approach

Five phases. One specialist. Published before you sign.

Every WordPress project I take on runs the same five phases: audit, diagnose, roadmap, execute and monitor. Here’s what happens at each one, what you get, and what I need from you in return.

The five phases

Audit, diagnose, roadmap, execute, monitor

A signed plan in about 15 days, then work that ships against it. Every phase ends with a deliverable you keep.

Phase 1: Audit

Days 1 to 5

I review your stack, hosting, content and search performance before recommending anything, because the real constraint is often not where you’d expect.

  • Stack & hosting review
  • Content inventory
  • Search baseline

DeliverableA baseline report: stack health, content gaps, and where the site stands in search today.

Your partAccess to analytics, hosting and the codebase.

Phase 2: Diagnose

Days 6 to 10

I sort every issue from the audit into what’s actually holding growth back and what just feels broken, and give each one an estimated impact.

  • Technical gaps
  • Content gaps
  • Growth gaps

DeliverableA prioritised gap register, scored on effort versus impact for every fix.

Phase 3: Roadmap

Days 11 to 15

A prioritised plan for the next quarter, sequenced by impact rather than by what is comfortable to tackle first. Every assumption is written down so it can be challenged.

  • 90-day plan
  • Owner per item
  • Written assumptions

DeliverableA signed-off execution plan with a shared dashboard for live progress.

Your partReview the plan, challenge it, then sign off.

Phase 4: Execute

Day 16 onward

Work ships against the roadmap, not around it. You own approvals; the roadmap owns velocity. A short check-in keeps both sides honest about what has moved.

  • Weekly progress
  • You approve
  • Monthly review

DeliverableShipped work against the roadmap, with a running log of what moved and what is next.

Your partTimely approvals, so the roadmap keeps its pace.

Phase 5: Monitor

Ongoing

Rankings, performance and content are not checked once and forgotten. Regular monitoring catches drops before they compound, and the roadmap is recalibrated against what is actually happening.

  • Regular checks
  • Drift alerts
  • Quarterly recalibration

DeliverableA running dashboard and a direct line for anything that needs attention.

The bargain

What I commit to, and what I ask of you

I commit to

Regular, visible progressNot a reveal at the end of a quarter. You see movement as it happens, or you know something is wrong.
Assumptions written downEvery roadmap decision is explained, not buried in a strategy nobody can question.
Honest timelinesIf approvals slip, the timeline slips, and that gets said out loud rather than papered over.

I ask of you

Access to the real stackAnalytics, hosting, the codebase, or an engineer’s time. Without it, the diagnosis is guesswork.
Timely approvalsReviews and sign-offs move at the pace the roadmap needs, or the roadmap slips with them.
A willingness to actRecommendations only work if they’re actually implemented, not filed away.

Terms

Capped by capacity, not locked by contract

I own every engagement end to end. That caps how many I can take on at once, and it’s the main reason I turn some briefs down. There are no long lock-ins: if the work isn’t moving, you should be able to leave.

3

Engagements at a time

5

Phases, every time

1

Named owner, end to end

0

Long lock-in contracts

Questions

Questions about how I work

What is the HelloSatya approach?

It’s the five-phase method I use on every WordPress project: audit, diagnose, roadmap, execute and monitor. You get a signed plan in about 15 days, then work that ships against it.

About 15 days. The audit runs on days 1 to 5, the diagnosis on days 6 to 10 and the roadmap on days 11 to 15. Work starts from day 16.

Yes. You keep the audit and the baseline report whether or not you go ahead with the rest of the work. The audit covers all five layers of your site, from foundation to trust.

I do. I own every engagement from the first audit to ongoing monitoring. On larger SEO and migration projects I bring in trusted specialists, and I tell you before I do.

No. There are no long lock-ins. If the work isn’t moving, you should be able to leave.

Access to the real stack (analytics, hosting, the codebase or an engineer’s time), timely approvals, and a willingness to act on the recommendations.

Up to three engagements at a time. That cap is the main reason I turn some briefs down.

Start with the audit

You get the assessment whether or not you engage further.