Engineering capacity · Seed to Series A

The free 30-day ship sprint

First PR merged by day 7. Then 23 more days of shipping.

A free 30-day engineering sprint for teams carrying more roadmap than headcount. We take real tickets off your board and merge them into production. You own everything, and there is no pitch at the end.

Start a conversation Two sprints run at a time

How the sprint runs

Thirty days, agreed in advance

Every sprint runs on the same schedule. You know what lands, and when, before you commit to anything.

  1. Day 0KickoffRepository access, a running environment, and the first ticket agreed in writing.
  2. Day 3Scope noteOne page: what we found in the codebase, what we are building, and what we are deliberately leaving alone.
  3. Day 7First pull request mergedReviewed by your team, approved, and landed in main. First check-in call the same day.
  4. Day 14Regression suite in CIAutomated coverage across the part of the system we have been working in, running on every change. Second check-in.
  5. Day 21Tickets two and threeScoped, built and merged the same way. Third check-in.
  6. Day 30HandoverDocumentation, a written summary of everything shipped, and twenty minutes of candid feedback.

Terms

There is no invoice. Here is what we ask instead.

What you receive

  • +Three to five merged tickets, each scoped to five working days or fewer
  • +A regression suite in your CI, yours to keep and extend
  • +Full ownership of every line written. No licence, no lock-in, no continuing dependency on us
  • +Three scheduled check-ins, on the dates above

What we ask

  • —That the work is actually used — merged and running, not parked on a branch
  • —Twenty candid minutes at the end: what worked, what did not, and what it was worth
  • —A reference, if we have earned one. If we have not, tell us plainly and we part on good terms

No payment, no card, no contract to renew. Those are the complete terms.

Fit

The sprint suits a particular kind of team

Well suited

  • +You are seed to Series A, with two to twenty-five engineers
  • +You have software in production that real users depend on
  • +There is an engineering role open that has stayed open longer than you planned
  • +Your CTO can decide without a committee

Poorly suited

  • ×You want a prototype or a demonstration. We merge into production, or the month was wasted
  • ×Nobody on your side has ninety minutes a week to review a pull request
  • ×The work cannot be scoped into five-day tickets
  • ×You need engineers in your timezone all day. We work to UTC+3

Guarantee

If the first pull request is not merged and working by day 7, we keep working at no charge until it is.

No invoice follows either outcome, so the guarantee is not about money. It is the only way to put our time behind the claim before you have seen us write a line of code.

Why free

A claim is not evidence

prepwise is a remote engineering practice. We build and ship production software — backend services, data and retrieval pipelines, integrations, test infrastructure, and the unglamorous work that turns something promising into something dependable.

We could tell you we are good at it. So could everyone else writing to your CTO this week. The only evidence worth anything is a merged pull request in your repository, reviewed by your own engineers, doing what it was scoped to do.

So that is the offer. Three teams, thirty days each, at no cost. We would rather spend a month demonstrating the work than a quarter describing it — and if it goes well, you will know precisely what you would be paying for the next time.

We take on two teams at a time.

Tell us what is stuck. If there is a ticket in it we can merge inside five days, we will say so — and if there is not, we will say that too.

Start a conversation We reply within one working day