No surprises in the invoice, the code or the timeline.

First meeting

Thirty minutes on Google Meet with an engineer, not a salesperson. You describe the problem; we ask the questions that decide the scope.

• Send a few paragraphs through the contact form or by email. We read every message and reply by email.
• If it looks like a fit, we set up a 30-minute Google Meet. Bring whoever knows the system best.
• If we're not the right team, we'll say so in the meeting, and point you somewhere better when we can.

You get: an honest read on whether we're the right team

Written proposal

Scope, what's out of scope, timeline, team and price on a few pages. Nothing starts until you've agreed to it.

• Audits, penetration tests and defined first releases are quoted at a fixed price.
• Longer product work is billed monthly for a named team, and you can scale it up or down with a month's notice.
• The proposal lists what we need from you: access, test accounts, a point of contact, decisions by certain dates.

You get: a fixed scope and price, or a monthly rate for ongoing work

The work

In your repository and your tracker. A short written update every week, and a demo at the end of each cycle.

• We work in your tools where possible: your GitHub or GitLab, your Jira or Linear, your Slack.
• The weekly update says what shipped, what's next, and anything blocked. Three short sections, no dashboards to log into.
• If the scope needs to change, we write down what changes and what it costs before doing it.

You get: a weekly update you can forward to your boss

Hand over

Code, documentation and credentials in your accounts, and a recorded walkthrough for whoever looks after it next.

• Documentation lives next to the code, so it gets updated with it.
• For security work: the final report and the retest results. For database work: before-and-after measurements.
• After hand over we're available for follow-up work, but you're never locked in.

You get: a system your team can run without us