//Process & engagement

How we work

Your repository, a reviewable release process, and terms agreed before work starts. Pick the engagement model that matches the work.

Three ways to engage us

Fixed-price, with discovery: A short paid or scoped discovery phase fixes the requirements, then we quote a fixed price and milestone schedule for the agreed work. Best for a defined deliverable — a codebase audit, a new platform, a migration.
Time and materials, with a cap: Billed for actual hours against an agreed monthly cap, reviewed and adjusted together as scope firms up. Best for ongoing development where the backlog will keep changing.
Embedded / dedicated team: Senior engineers join your repository, tracker and review process as extra capacity, sized to your roadmap. See the embedded team details below.

Whichever model you choose, prepayment starts from 25% and milestones are fixed in the contract before work begins.

//Extra engineering capacity

You have in-house engineering ownership but need more capacity than hiring can provide in time.

The work spans multiple releases and needs engineers participating in planning, reviews and delivery.

If the product has no engineering owner or cannot be released safely, start with a codebase audit or takeover instead.

Team size: Sized around your backlog and stack — typically one to a few senior engineers, all with 5+ years of experience.
Tools: Work stays in your repository, tracker (Jira, Linear or similar) and chat. Nothing moves to our tools.
What to send us: A stack summary, your current team, the next release goals, blockers and target dates. A brief description is enough to begin.

Who you talk to: The lead engineer on your project speaks with you directly — in English, on calls and in writing. Not a separate account manager relaying messages.
Working hours & overlap: Our team works 10:00–19:00 EET/EEST. That gives at least 4 hours of overlap with EU business hours and the US East Coast morning, in addition to full UK overlap.
Written progress: On active engagements, a weekly update covers what shipped, what is next, blockers and effort against the estimate.

A shared workflow makes each change easy to review and follow.

01
Agree the outcome
Record the scope, acceptance checks and dependencies before implementation.
02
Review the change
Code changes arrive as pull requests in your repository, with checks and context for the reviewer.
03
Release and verify
Agree who deploys, what is monitored and how to roll back. Check the affected workflow after release.

Code and infrastructure: You own the repository and infrastructure accounts from the first commit, not at hand-off. Your GitHub organization, your cloud account, your credentials.
Payment terms: Prepayment starts from 25% of the agreed price; milestones and their payment schedule are fixed in the contract before work begins. Payment is by official invoice and bank transfer; we do not take card or wallet payments.
Warranty: Work delivered under a fixed-price milestone carries a one-month warranty against defects in that delivery.
Data processing agreement: We can sign a DPA on request for EU/UK client data. We do not claim full GDPR compliance or an ISO certification we don't hold — ask for the DPA and we'll send it before you share any personal data with us.

Coverage and response: Agree coverage hours, severity levels, escalation contacts and response targets as part of the support scope. Response time and time to resolution are separate commitments — support is not a guaranteed uptime SLA.
Incident ownership: Identify the engineer handling an incident and where progress will be reported. Agree the route for urgent requests before an outage.

Start with a codebase audit, discuss a new platform, or ask about an embedded team. The introductory call is free.