AI development sprint
Your next software release, working 15 days after the kickoff workshop.
You bring the release you already want. We write the requirements with you, build for ten working days, and hand it back running. Fifteen days from the workshop, matching the document you signed off, or we refund your fee.
Fifteen days from the kickoff workshop. Not fifteen days from your first email. The clock starts the day we sit down and write the requirements together.
The scope is written down before a line is built. You sign off one document at the workshop. What we hand back is checked against it, item by item, in front of you.
The Sprint Delivery Guarantee. On time, matching that document, and at least 75% below the development cost we agree in writing for the same scope. Miss any of it and you get your fee back.
Free call, no obligation. You leave it knowing what your next release would take and what another quarter of waiting costs you, whether or not you hire us.
The release that keeps moving to next quarter
You have a feature list everyone agrees on. The estimate came back in months. The quote came back bigger than the feature is worth, and the work still has not started.
So the release slips. It slips again at the next planning meeting. The people who asked for it stop asking, and the thing you needed in spring is the thing somebody else shipped in summer.
The invoice is the smaller half of what that costs you. The larger half is the quarter you spent waiting, and the decisions you postponed because the software was not there to make them with.
How fifteen days is possible
We write the requirements down first, in one workshop, with the people who will actually use the software. That document is the scope, the test list and the acceptance criteria at the same time. Most of the time a software project burns is spent discovering what was wanted.
Then AI drafts the code, and we review, test and correct every line of it before it goes near your repository. The machine is fast at typing and careless about edge cases. We are the opposite, which is why the split works.
That is why the estimate is fifteen days. The typing was never the slow part. The deciding was, and we do it on day zero with you in the room.
What you get
One fixed scope, agreed in writing before anything is built.
A requirements workshop, four to eight hours. We sit with you and the people who will use the release, and write down exactly what it has to do. You sign that document before we build anything.
A ten-day build sprint. The release itself, built and tested against the requirements you signed. You see working software partway through, while changes are still cheap.
A presentation day at the end. We walk the release against the document, item by item. Your feedback is collected the same day, in the same room.
Next steps, in writing. What the next sprint would build, what it depends on, and what your own team can do without us. Take that list anywhere you like.
A fee fixed before the sprint starts. Agreed in writing at the workshop, against the scope in the document. It does not move because the build turned out harder than we expected.
What the fifteen days look like
Day 0
The kickoff workshop. Four to eight hours. We write the requirements, agree the scope, and write down the baseline the guarantee is measured against. The clock starts here.
Working days 1 to 8
The build. You get a working version to look at partway through, not a surprise at the end.
Working days 9 and 10
Testing against your real cases and the fixes that come out of it.
Working day 11
The presentation. We walk the document item by item, take your feedback, and hand you the next steps in writing.
Eleven working days after a Monday workshop is the fifteenth calendar day. That is where the fifteen comes from, and it is counted from the workshop. If we are waiting on access we do not have yet, the clock pauses, and we tell you the day it happens.
The Sprint Delivery Guarantee
We deliver on day fifteen, counted from the kickoff workshop, matching the requirements you signed, with defects fixed at no cost, at a development cost at least 75% below the baseline agreed in writing for the same scope. Miss any of the four and we refund your fee.
On time, counted from the workshop. Day fifteen is a date in the contract. It moves only when you ask for a change or we are waiting on access from you.
It matches the written requirements. The document from the workshop is the test. We walk it with you on the presentation day, item by item. Anything missing is missing.
Defects are fixed at no cost. Anything that fails to do what the requirements say it does, we fix, and you do not pay for the fix. Nobody can promise software with no defects in it. This is the promise that stands behind that one.
The baseline is written down before we build. At the workshop we cost the same scope the conventional way, in developer days at the rate you tell us. That number goes into the contract, and the 75% is measured against it. Neither of us can move it later.
How you claim. Email info@fijisolutions.net within thirty days of the presentation day, with the numbers we agreed. You get an answer within ten working days.
These terms go into the contract before we build, in these words. The 75% is a promise with a refund behind it, measured against a number we both agree before the sprint starts. It is not a report of what past clients got.
Who this is for
This is for you if
- You own the business, or you can sign off a scope without taking it upstairs.
- There is a release you already want, and somebody can describe what it has to do.
- You can give four to eight hours to the workshop, with the people who will use the software.
- You can give us access to the systems the release touches.
This is not for you if
- You want a whole platform rebuilt. That is a different engagement and a different conversation.
- The requirements are still an argument between two people. Settle it first, then book the workshop.
- Nobody internally can spare four to eight hours on day zero.
- You want the sprint without the baseline. The guarantee is built on the baseline.
The questions we get asked
- What does it cost?
- We quote it after the first call, in writing, against the scope we agree at the workshop. There is no list price and no rate card, because costing a release before seeing it is guessing. The fee is fixed before the sprint starts and it does not move afterwards.
- Fifteen days from when?
- From the kickoff workshop, never from your first email. Between your first message and that workshop there is a call and a scoping round. How long those take depends mostly on how fast your requirements settle.
- Who owns the code?
- You do. It is written straight into your own repository, so the code is yours from the first commit. The scope you sign at the workshop says so.
- Is AI writing our software unsupervised?
- No. AI drafts, we review, test and correct. The speed comes from the drafting. The safety comes from the review, and the review is the part you are paying for.
- What happens after the fifteen days?
- You decide. Two doors are open: another sprint with us, or the next-steps document goes to your own developers. It is written so either works, and you are under no obligation to continue with us.
Tell us what the release has to do
Describe the release you want out of the door. We come back with what it would take to build it in one sprint.
Free, no obligation, no sales pitch.
Prefer to skip the form? Book the call directly: Pick a time on Calendly
Free call, no obligation. You leave it knowing what your next release would take and what another quarter of waiting costs you, whether or not you hire us.
We reply within one business day.