How I Work
Every project is different — but the way I run them isn't. Here's exactly what working with me looks like, from first message to final handoff.
Before We Start
You reach out via contact form or WhatsApp.
I review your message and respond within 24 hours.
We schedule a 30-minute discovery call — free, no obligation. I listen more than I talk.
If there's a fit, I send a written proposal and SOW within 3–5 business days.
“I'm honest about fit. If your project isn't right for me, I'll tell you — and where possible, point you in a better direction.”
The Proposal & SOW
A typical Statement of Work contains: scope definition, milestone breakdown, deliverable list, payment schedule tied to milestones, timeline estimate, and out-of-scope items explicitly listed.
You only pay when a milestone is delivered and approved — never upfront for work that hasn't happened.
Milestone-based billing is better for both parties. You get predictable costs and real deliverables at each stage. I get clear targets and no ambiguity about what “done” means. If a milestone needs revision, we agree on what changes before I start — not after.
How We Communicate
Async-first, never silent. You won't wonder where the project is.
Primary channel
Slack or email — your preference
Status updates
Weekly written update every Monday
Documentation
Shared Notion workspace — always up to date
Scope changes
Written amendment before work starts — always
“You'll always know where we are. No chasing required.”
Milestone Delivery
I complete the milestone deliverable
I share it with you for review
You have agreed business days to request revisions or approve
On approval, the milestone payment is triggered and the next milestone begins
Revision policy: typically 2 rounds of revisions per milestone, defined in the SOW.
Handoff & Documentation
At the end of every engagement, you receive:
- ✓Working, tested deliverable
- ✓Full technical documentation written for the next developer
- ✓A recorded walkthrough session
- ✓Clean codebase with comments
- ✓Post-launch support period (duration specified in SOW)
“I write code and documentation as if someone else will maintain it — because they will.”
What Makes This Different
I flag problems early — not after they've become expensive.
Documentation is part of the deliverable, not an afterthought.
I don't disappear after handoff.
Scope changes are handled in writing, every time.
FAQ
Ready to start a conversation?
The first step is a message. The second is a 30-minute call. We go from there.