Nadia Mohamed
Approach
Async-first, documented, designed to outlive the engagement
How I run engagements — small enough to keep the depth real, structured enough that you always know where the work stands. Three retainer clients per quarter, maximum.
The five-step process
Every engagement runs through the same five steps. Scope and duration vary by service; the shape stays the same.
- 1
Discovery
Deep dive into business goals, the current technical setup, and the constraints that matter.
1 week - 2
Strategy
A data-driven plan that fits your stack and the market — not a generic playbook.
1 week - 3
Implementation
Hands-on execution with regular updates. Code merged, schema deployed, dashboards shipped.
Variable - 4
Tracking
Measurement infrastructure that proves what moved — and what didn't.
Ongoing - 5
Optimization
Continuous improvement based on what the data shows after the build lands.
Optional retainer
Tools & communication
Async-friendly by default. One scheduled sync per engagement is usually enough; everything else is documented in the tools your team already uses.
Tools I work in
Working principles
Async-first
Work across time zones without daily standups. Updates land in your shared workspace; one scheduled sync mid-engagement.
Documented
Every decision recorded with the reasoning. The artefact your team inherits is a system, not a black box.
Self-managed
No micro-management. The engagement runs against scope and outcomes, not against hours.
Three retainers, by choice
A hard limit on concurrent retainer clients per quarter. The cap is how the depth stays real.
Who this works for — and who it doesn't
Engagements are tight enough that not every team is the right fit. Being honest about this upfront saves both sides.
Who this works for Best fit
- Teams that ship — engineering is the bottleneck, not the unknown
- Marketing leaders who want depth, not a slide deck
- Async-comfortable cultures where written-down beats meeting-driven
- Decision-makers who can sign off without three rounds of internal review
- Companies that have a budget for one senior consultant rather than an agency retainer
- SaaS, edtech, B2B and tech brands with real technical surface area
Who this doesn't Better elsewhere
- Teams that want daily check-ins and a constant Slack presence
- Stakeholders who prefer slide decks over workbooks
- Projects where the SEO need is content production rather than technical architecture
- Brands at the very start of their content journey — content investment comes first
- Companies that need a multi-person agency for parallel workstreams
- Engagements requiring on-site presence — I'm remote-only
The cadence, week to week
What a typical retainer looks like from the outside.
Week ahead
A short written update — what's shipping this week, what I need from you, what's blocked. Posted in your shared workspace, not in a meeting.
Async progress
Mid-week, work-in-progress visible. PRs in review, dashboards taking shape, decisions documented as they're made.
What shipped
End-of-week recap — what landed, what didn't, what's pencilled in for next week. Plus any decisions that need your input over the weekend.
Sound like the right way to work?
Start with a free SEO + GEO health check or get in touch directly — I'll come back within a business day with whether one of the services is the right fit.