AI prototype for one use case
See what AI is actually worth here, on one use case, two weeks from the kickoff workshop.
You pick the use case. We build a working AI prototype on your data and measure it against what that work costs you today. Two weeks from the kickoff workshop, and at least 75% lower cost, or we refund your fee.
One use case, not an AI programme. You choose it in the workshop. Reading supplier documents, drafting quotes, triaging tickets, whatever costs most by hand.
Two weeks from the kickoff workshop. Not from your first email. The clock starts the day we write the requirements together.
The Proven-Savings Prototype Guarantee. We write down what that work costs you today. Miss 75% against that number and you get your fee back.
Free call, no obligation. You leave knowing whether your use case is worth building and what it would take.
The AI decision nobody can make on paper
Everyone in the building has an opinion about AI. The board wants a plan. A vendor wants a nine-month programme and a signature first. Nobody can tell you what it is worth in your business, on your data, on the work your people do every day.
So the decision waits. It waits through another quarter of slide decks and pilots that never touch a real process. The same work carries on by hand, at the same cost.
The real question is narrower. Does this work here, on this use case, at a number worth paying for? One use case is enough to answer it. Postponing it means another year of opinions.
How two weeks is possible
We do not start with a blank page. We start with one use case, written down as requirements you sign off, and build on models and platforms that already exist. Nothing is trained from scratch.
The build is AI-assisted on our side too. Code generation writes the first pass. We review it, test it against your real cases, and refine it. That is what takes the months out.
The measurement runs beside the build. We record what the use case costs today in the workshop, and judge the prototype against that number at the end.
What you get
One fixed scope, agreed in writing before anything is built.
A requirements workshop, four to six hours. We define the use case, the data it touches, and what success means as a number. We leave with what the work costs you today.
The build sprint. The prototype itself, built and tested on your real cases rather than a demo dataset.
A presentation session, two to four hours. We run it in front of the people who decide, show the measurement against the baseline, and set out what production would take.
Working software and the source code, in your name. It runs, and you can put it in front of a board, a client or the team that would use it. The code is yours to keep.
Written documentation. What it does, what data it uses, where its limits are, and what production would need.
What the two weeks look like
Day 0
The kickoff workshop. Four to six hours. We write the requirements and record what the use case costs today. The clock starts here.
Days 1 to 8
The build sprint. You see a working version partway through, not a reveal at the end.
Day 9
Testing on your real cases, the fixes that follow, and the measurement against the baseline.
Day 10
The presentation. Two to four hours, with the people who decide in the room, and a written view of what production would take.
Ten working days is two calendar weeks, counted from the workshop. If we are missing data or access, the clock pauses until we have it.
The Proven-Savings Prototype Guarantee
The prototype arrives on time, matches the requirements you signed, and shows at least a 75% cost reduction for the agreed use case against the baseline measured in the workshop. If not, we refund your fee.
This is a promise, not a past result. The 75% is what we commit to for your use case, with a refund behind it. It is not a figure measured on somebody else’s project.
The baseline is measured before we build. In the workshop we count what the use case takes today and what that time costs. That number goes into the contract.
On time, and to the requirements. Two weeks from the workshop, against the requirements you signed. If we are waiting on data or access from you, that time does not count. Miss either and we refund your fee.
Defects are ours. We fix any defect against the agreed requirements at no cost.
How you claim. Email info@fijisolutions.net within thirty days of the measurement. You get an answer within ten working days.
These terms go into the contract before we build, in these words.
Who this is for
This is for you if
- You have a budget line for AI, or you are about to justify one.
- You can name one use case that costs real money by hand today.
- You can decide without a six-month committee.
- You can give us the data, or a realistic sample of it.
This is not for you if
- You want a company-wide AI strategy. This is one use case.
- The use case has no data behind it yet.
- Nobody can spare four to six hours for the workshop.
- You want the prototype without the measurement.
The questions we get asked
- What does it cost?
- We quote it after the first call, in writing, against what your use case needs. There is no list price and no rate card, because scoping a use case without seeing it is guessing. The fee is fixed before we build.
- Is a prototype just a demo?
- No. It runs on your data and your real cases, and you keep the source code. What makes it a prototype is scope: one use case, without the edge cases and integrations a production system needs.
- What if it shows AI is not worth it here?
- Then you have your answer for the cost of two weeks instead of a year, and you keep the code, the documentation and the baseline numbers. The guarantee covers that too. No 75%, no fee.
- Who owns the code and the data?
- The code we write is yours. Your data stays yours, and we agree in writing which data may reach which model provider before anything is processed.
- What happens after the two weeks?
- Three doors, and you pick. Stop here with the answer. Take it to an MVP. Or go to a full build with the same team. Nothing from the prototype is thrown away.
Tell us the use case
Name the work you would test AI on first. We will come back with what a prototype would take and what it would have to save to be worth it.
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 knowing whether your use case is worth building and what it would take.
We reply within one business day.