Technically demanding presales
I review scope, dependencies and risk before the agency commits to a solution or date.
I join an existing project to take on a defined delivery. We agree on my scope, who signs it off and what the team needs to continue.
I reproduced the +DERA app, backend and website to investigate issues and prioritise the next work.
Read the diagnosisA diagnostic environment with anonymised data.
23 actionable items identified in the issue log to guide further development.
I first review the objective, current state, dependencies and availability, then propose an entry point with a clear acceptance condition.
I review scope, dependencies and risk before the agency commits to a solution or date.
I review the existing code and take on the website, app feature or integration holding up the project.
Temporary capacity within an agreed window; critical on-call work or urgent support is scoped explicitly.
Your team receives the agreed changes, checks and documentation needed to maintain the work.
Scope, access, owners, availability, risks and the acceptance condition are visible from the start.
Code, tests, error states and validation of the flow that will actually ship.
I document configuration, decisions and remaining work so another developer can take over.
Tell me about the project
Objective, current state and timing are enough to assess fit and suggest a concrete starting point.
A human reply, normally within one business day. No automatic addition to marketing lists.
Yes. I can stay out of client-facing communication, work under an NDA and follow the agency’s channels and procedures.
The objective, deadline, current state, approval owner and the technical work blocking delivery. That is enough to suggest a starting point.
Yes. I review the existing codebase, take responsibility for an agreed part and document the handover.
They are delivered under the terms agreed with the agency, ready for release, maintenance or handover to the relevant team.