we/need/a/dev

For product and platform teams

We fix
what exists.

Your team has a product to build, a migration to finish, or a deployment that keeps breaking. We handle the application, APIs, and cloud infrastructure on AWS or Google Cloud. We use your project board and code review process.

We scope and quote before you commit. Nothing is due until the scope is agreed.

EngagementScoped and quoted first
Working session$1,250 · 10 hours prepaid
Reserved capacityFrom $4,500 · 40 hours / month
CommitmentMonthly, cancel with notice
Time zoneDenver, overlaps US and EU mornings
ReportingWritten weekly, no status meeting
01Scoping call with the lead
02Written scope and quote
03Least-privilege access
04First commit inside the week
Ways to engagePriced after a scoping call

Three shapes.
One team.

Which one fits depends on whether you need work taken off your plate, hands inside your team, or someone accountable for the technical direction. Every shape runs through one senior lead, with a specialist pulled in when that makes the work better.

01

Defined delivery

We take a defined piece of the roadmap and return it finished. You review at the boundaries and do not manage the work day to day.

  • Fixed scope, fixed schedule
  • Our repository or yours
  • Weekly written update
Best for a backlog you cannot reach
02

Embedded capacity

Reserved senior hours inside your team: your board, your standups, your review process, your definition of done.

  • Reserved hours per week
  • Your tools and process
  • Monthly, cancel with notice
Most common arrangement
03

Fractional lead

Someone accountable for architecture, review, and technical decisions while you hire, or while a permanent lead comes up to speed.

  • Set days per week
  • Architecture and code review
  • Hiring support if you want it
Best during a gap or a rebuild

Every shape is priced after the scoping call. The entry point is a $1,250 working session · 10 hours prepaid; reserved capacity starts at $4,500 a month for 40 hours; production rescue is $175 per hour · 4-hour minimum.

What we take on

The work nobody
has time for.

Bring the thing that has been on the roadmap for three quarters. We are most useful where the code already exists and the risk is real.

01

Migrations

Framework, database, or cloud moves done incrementally, with a way back at every step.

02

Integration backlog

The third-party APIs, sync engines, and webhooks that keep breaking quietly.

03

Deployment and reliability

CI/CD nobody trusts, missing observability, and the incidents that keep repeating.

04

Platform work

Internal tooling, shared services, and the unfinished platform your product teams wait on.

05

AI in production

Taking a working prototype to something with permissions, monitoring, and a support path.

06

Production rescue

A system that is failing now. We start with containment, then fix the cause.

Access & security

We ask for
as little as possible.

Procurement usually stalls on access. Here is our default position, so your security team can read it before the first call rather than after it.

Least privilege

We ask for the narrowest access that lets us do the work, and we tell you what we no longer need as the project moves.

Your accounts

Work happens in your repositories, your cloud, and your ticket system wherever possible. Nothing important lives only with us.

Named people

You know who is on the work. No unnamed subcontractors and no rotating staff without telling you first.

Offboarding

Access revoked and confirmed in writing when the engagement ends, with a handover document for whoever picks it up.

Paperwork

We sign your NDA, MSA, and DPA. If your security review needs a questionnaire filled in, we fill it in.

AI tooling

We say plainly which assistants we use and on what code. If your policy forbids it, we work without them.

Selected workPublic, linked, conservative

Built in the
real world.

Named projects, at the level we can say in public. Follow the link for more.

03

Consumer AI / platform

Current work spotlight

Current platform and AI work with HowMuch Group, shared only at the public, high-level product direction.

Senior AI and platform engineeringHowMuch Group
Explore public project sources

How it starts

One call,
then a written scope.

Forty-five minutes with the technical lead, not a salesperson. You describe the problem and the constraints. We tell you whether we are the right people, and what we would do first.

Book a consultation

Or email nick@weneedadev.com with what you are dealing with.

For product and platform teams

Tell us what
is stuck.