Services
Ways to work together
Two questions, answered separately: what you are trying to accomplish, and how much help you want doing it. They are not the same question, and a restaurant owner and a CTO can land on the same goal needing very different engagements.
What do you need help with?
Review what I have
You already have a site, a product, or an internal system, and you want someone experienced to look at it and say what is actually worth fixing first.
- Where customers get stuck or give up
- Accessibility obligations you have not met yet
- Frontend and product quality
- Architecture that is getting harder to change
- Steps in a workflow that cost more than they should
- Whether AI would help here, or just add a moving part
Usually starts with quick fit call, strategy session, assessment and roadmap.
Talk about thisHelp me automate this
Something gets done by hand that probably should not be. The first question is whether software earns its place at all, and often enough the answer is no.
- The same information typed into three systems
- Reports assembled by hand every week
- Follow-up that depends on somebody remembering
- Tools that do not talk to each other
- Approvals and paperwork that stall
Usually starts with quick fit call, strategy session, focused implementation.
Talk about thisBuild or modernize something
One bounded piece of work with a definite end: something new that needs building, or something existing that has outgrown the way it was built.
- React and frontend architecture
- A component system that never got adopted
- Accessibility work with a deadline attached
- Booking, checkout or customer flows
- Dashboards and data visualization
- Internal tools and integrations
Usually starts with quick fit call, focused implementation, assessment and roadmap.
Talk about thisMake my product agent-ready
Your software is going to be used by AI agents, whether or not you planned for it. This is the engineering that decides what they can reach and what happens when they get it wrong.
- Which capabilities should become tools, and which should not
- Exposing them through an API or MCP
- Permission boundaries and human approval points
- Audit trails and observability
- Evaluating whether it actually works
- Undoing an action that should not have happened
- Local inference where data cannot leave the building
Usually starts with quick fit call, strategy session, focused implementation.
Talk about this
How do you want to work together?
Quick fit call
No charge10 to 15 minutes
A short call to work out whether I am the right person for this, and which kind of engagement fits. No deck, and no homework on either side.
Book a quick fit callWhat you get
- A clear read on what you are actually trying to solve
- Whether this is work I should take on, said plainly
- Which engagement fits, and roughly what it would involve
- A rough range if the work is already well defined, or what I would need to know to give one
Strategy session
$200 per session indicative60 minutes
An hour on one specific problem, with material sent ahead and reviewed before we meet. This is advisory time rather than an introduction, which is what separates it from the fit call.
Register interestWhat you get
- You send context in advance and I go through it before we talk
- A full hour on your problem, not on getting acquainted
- A shared read on the actual problem, not the presenting symptom
- Specific recommendations, written up afterward
- A proposed next step, whether or not you hire me for it
Focused implementation
Scoped per engagement1–3 weeks, fixed scope
One bounded problem, scoped before anything starts, ending in something that works. A framework migration, a component system nobody adopted, an accessibility gap with a date on it, or a customer flow that needs to exist.
What you get
- A defined deliverable agreed before we start
- Working code, not a slide deck
- Documentation your team can carry forward without me
Register interestThe goal is not to create dependency. It is to strengthen the foundation and give your team momentum they keep after the engagement ends.
Typical areas: frontend modernization, React migration planning and implementation, component system evaluation, accessibility improvements, architecture review, performance and maintainability work, or a practical assessment of where AI genuinely fits in your product.
Assessment and roadmap
Scoped per engagement1–2 weeks
For when you are not ready to start building. A review of where things stand and a prioritized plan, so the next decision gets made with better information than it would have had.
Register interestWhat you get
- Current-state review, scoped to what you actually run
- Risks, bottlenecks and accessibility considerations, named plainly
- A prioritized roadmap with recommended sequencing
Fractional technical partner
Scoped per engagementMonthly retainer
Ongoing technical and product guidance for teams that need senior judgment regularly but not a full-time hire. Defined hours, defined scope, defined communication expectations.
What you get
- A reserved amount of time each month, agreed up front
- Architecture and frontend strategy input on live decisions
- Team enablement rather than a second backlog
Register interestA retainer reserves a defined amount of my time each month for technical guidance, implementation, and prioritized work. Requests outside that scope can be scheduled separately.
This is deliberately not framed as another employee. Clear boundaries are what make the arrangement work for both sides.
How it works
Say what you need
Pick the goal that sounds like your situation, or describe it in your own words.
Talk briefly
A short call to check I am the right person and work out which engagement fits.
Define the work
Scope, deliverable and end date agreed before anything starts.
Continue only if it helps
Most work ends cleanly. A retainer is for when it genuinely should not.
Common questions
- How do engagements usually start?
A strategy session. It is a paid hour, which keeps it focused, and you leave with a recommendation whether or not we work together afterwards. If a sprint or assessment makes sense, we scope it from there.
- What does “fixed scope” actually mean?
We agree the deliverable before the work starts, in writing. Change is normal, but it gets handled explicitly rather than absorbed silently — which is what keeps a three-week engagement from quietly becoming a three-month one.
- Do you work with non-technical founders?
Often. A good part of the value is translating between the business problem and the technical one, in both directions. You do not need to arrive with a technical spec.
- Are you available for full-time roles?
I am focused on consulting engagements, but I am open to the conversation. The résumé and full work history are on this site if that is what you are here for.