Every consultant claims they're "results-oriented" and "client-focused." Those words mean nothing without specifics. Here's exactly how I work, so you know what you're getting.
Why Process Matters
Bad consulting fails in predictable ways. Scope creeps. Deadlines slip. Communication goes dark. The client ends up with a half-finished deliverable and an invoice for twice the original quote.
Good consulting avoids those failures by design. Not through heroic effort or good intentions—through process. Here's mine.
Phase 1: Discovery
Before I quote anything, I need to understand the real problem.
What I'll ask you:
- What are you trying to accomplish? (The business goal, not the technical task)
- What have you tried already?
- What does success look like?
- What's your timeline?
- Who else needs to be involved?
These questions matter because technical problems rarely exist in isolation. A "simple bug fix" might actually be a symptom of architectural debt. A "quick feature" might require changes across three services. Understanding context prevents expensive surprises later.
What you should expect:
- A response within 24 hours of your initial contact
- Follow-up questions if anything is unclear
- Honest feedback if I think the project isn't a good fit
- No sales pitch—I'll tell you what I think, not what you want to hear
Discovery usually takes one or two email exchanges. Sometimes a short call if the problem is complex. The goal is alignment: we should both understand exactly what we're doing before any work starts.
Phase 2: Scoping
Once I understand the problem, I write a scope document. This isn't a contract—it's a shared understanding.
A scope includes:
- Deliverables. Exactly what I'll produce. Not "improve performance" but "optimize the three slowest API endpoints to respond in under 200ms."
- Timeline. When you'll get each piece. I break work into milestones you can verify.
- Price. Fixed, not hourly. No surprise invoices.
- Assumptions. Things I'm taking for granted. If these turn out to be wrong, scope changes.
- Out of scope. Things I'm explicitly not doing. This prevents creep.
Why fixed pricing:
Hourly billing creates bad incentives. You start wondering if I'm padding hours. I start wondering if I should mention that extra edge case. Fixed pricing aligns us: I want to finish efficiently, you want quality results, nobody's watching the clock.
What you should expect:
- A written scope within 48 hours of finishing discovery
- Clear enough that you could hand it to another developer and they'd know what to build
- Room for one round of revisions before we finalize
- A start date once you approve
If the scope looks right, we agree and I start. If it doesn't, we adjust until it does. Either way, we're aligned before any work begins.
Phase 3: Delivery
This is where most consultants go dark. You hand over money, they disappear into a cave, and you hope something good emerges. I don't work that way.
Daily updates:
Every day I'm working on your project, you get a status update. Short—usually 3-4 sentences. What I did, what's next, any blockers. You always know where things stand.
Incremental delivery:
I break work into small pieces and ship each one separately. A week-long project might have three or four commits you can review as I go. This means:
- You catch misunderstandings early, before they compound
- You can give feedback throughout, not just at the end
- If something changes on your side, we haven't wasted days going the wrong direction
Clean code:
Every deliverable includes tests and documentation. The code I hand off is ready to merge—not "works on my machine" ready, but production ready. Comments explain why, not just what. READMEs cover setup and maintenance.
What you should expect:
- Work delivered as pull requests to your repository
- Tests that prove the code works
- Documentation your team can actually use
- Code that follows your existing conventions, not mine
I adapt to your stack and your workflow. If you use GitHub, I open PRs. If you use GitLab, I open merge requests. If you have a style guide, I follow it. You're not learning my system—I'm fitting into yours.
Phase 4: Communication
Communication isn't a phase, really. It's woven through everything. But it's important enough to call out separately.
My commitments:
- Response time under 24 hours, usually faster
- Proactive communication—I reach out before you have to ask
- Honesty about problems. If something's going wrong, you'll hear about it immediately, not at the deadline
- Async-first. Email or Slack. No mandatory calls unless the situation genuinely requires them
What kills consulting relationships:
Silence. When a consultant stops responding, trust evaporates. Even if they're doing great work, the client assumes the worst.
I don't do silence. If I'm stuck, I tell you I'm stuck. If I'm ahead of schedule, I tell you that too. If I realize the scope needs to change, we talk about it immediately.
What you should expect:
- Knowing the status of your project at any moment
- Never having to chase me for updates
- Direct answers to direct questions
- No jargon, no obfuscation, no hiding behind complexity
After Delivery
The engagement doesn't end when I merge the PR.
Included in every project:
- One round of revisions within the original scope
- 30 days of bug fixes for anything I built
- Documentation handoff to your team
- Availability for questions as you integrate the work
What's not included (but available):
- Extended maintenance or support (quoted separately)
- Additional features beyond original scope (new project)
- Training your team on the codebase (available as an add-on)
What Makes This Different
Most consultants optimize for billable hours. I optimize for results delivered per engagement.
I want to solve your problem efficiently and move on. You want quality work without ongoing dependency. This alignment means I'm not trying to extend the engagement—I'm trying to finish it well.
I don't do staff augmentation or ongoing embedded work. I do projects: clear scope, defined deliverables, fixed timeline. This means I attract clients who know what they want and value speed. If that's you, we'll work well together.
Ready to Start?
If you have a specific problem and want it solved well, let's talk. If you want more detail on what I charge and why, see pricing. If you want to see how I've worked with others, check my process page.
No calls required. Just email me what you need and I'll respond with questions or a quote.
That's the whole process. Specific, transparent, and designed to avoid the failures that make consulting painful. If it sounds like what you're looking for, reach out.
If you're a developer learning to consult, check out my Junior Developer Pricing Guide — a complete guide to pricing your first freelance projects with formulas and sample quotes.