Pilot programme
Run Parity on one of your real projects. Free.
We are working with a small number of pilot partners at a time. It starts with a 30-minute conversation about one real project. Then Parity turns your signed requirements document into an epic, user stories and acceptance criteria on your own Jira or Azure DevOps board, and you tell us honestly how close it got.
Two free tokens, unlocked after your pilot call. A maximum of 2 hours of your time across seven days. No card.
Why we are asking
It works. We want to know how well it works on yours.
Parity takes a signed requirements document and uploads structured user-stories directly on to your board in about 99 seconds. What we cannot test on our own is how it behaves on your templates, your domain and your awkward edge cases.
We are not asking you to buy anything. We are asking you to try it on one project and tell whether it can be embedded into your ways of working. That feedback shapes what we build next, and you get to see the result on your own numbers before money is mentioned.
A free pilot only works if both sides are in sync, so we ask for a real conversation first. Thirty minutes to understand the current process, agree the project, what success looks like and who decides. Then the two tokens are yours.
"The first time we saw Parity turn requirements into a structured backlog, it was obvious this handover didn't need to stay manual."
What delivery teams keep telling us
- Developers have got faster with AI. The write-up in front of them has not.So the slowest step has quietly moved to the start of every project.
- The real deadline is not refinement. It is the afternoon before.Stories need to reach developers and testers a day early so the session is quick. That is when the pressure lands.
- Plenty of teams keep a BA a sprint ahead to hide the gap.It works, until volume goes up and nobody is spare.
- Almost nobody has measured how long the write-up takes.Most people guess somewhere between three and seven days a document.
- The first question is always: how long will I spend checking it?Fair question. It is exactly what the pilot measures.
What changes with Parity
Product overview.
Parity does not remove discovery, product judgement, technical discussion or refinement. It removes the repetitive drafting work required to get the team to the point where delivery can commence.
Why this matters
The objective is not simply to “write User Stories faster”. It is to recover delivery capacity. By reducing the manual effort between approved requirements and backlog readiness, teams can:
Start refinement sooner
Reduce the time between requirements approval and meaningful delivery planning.
Improve consistency
Create a more repeatable starting point across projects and teams.
Increase the leverage of the existing team
Create more usable delivery capacity before defaulting to additional headcount.
Refocus specialist time
Allow Business Analysts, Product Owners and delivery leads to spend more time on analysis, stakeholder alignment and delivery decisions.
Reduce key-person dependency
Make backlog preparation less dependent on one individual’s availability and writing style.
How the pilot works
A conversation first. Seven days.
One decision at the end.
Nothing changes about how your team refines or estimates. Parity only changes when the tickets exist.
Apply
Two minutes. Tell us about your team, your board and the kind of documents you work from.
You: fill in the form below.
Pilot call
We agree four things: the project, the signed document you will use, what the pilot has to prove, and who decides at the end. We book the decision call there and then. Your two free tokens are unlocked on this call.
You: bring whoever will make the call on carrying on.
Set up
We connect one project to your Jira or Azure DevOps board. Credentials by email, a short PDF guide and a ten-minute walkthrough. We note how long a write-up takes you today, so we have something honest to compare against.
You: name a pilot lead, a board admin, your delivery manager and the BA who will run it.
Run it
Run a recent signed document and a live one. Your BA and delivery manager review what Parity produced, what they changed and how long checking took. We record that session so the evidence is in your own words.
You: two documents and about an hour of review.
Decide
The call you booked in step 2. We play back your numbers against what you said the pilot had to prove. Then you choose: carry on as a founding partner, extend the pilot, or stop. Stopping is a perfectly good answer.
You: 30 minutes, and the decision-maker you named.
The one question the pilot answers: how much would your analyst change before that went on the board? That is why we run it on your document, not ours.
The deal, both ways
Free, but not casual.
The most effective pilots are the ones where both sides deliver. So here is exactly what each of us signs up to.
What you get
- Two free tokens: two of your documents turned into a reviewable backlog on your board.
- One project connected to your Jira or Azure DevOps, set up with you.
- A founder on hand for the whole seven days.
- Your own numbers played back to you: time today, review time with Parity, what changed.
- Founding-partner pricing if you decide to carry on.
What we ask of you
- A 30-minute pilot call before we unlock the tokens.
- One real signed requirements document. An anonymised one is fine.
- A named person who can decide whether to carry on.
- The decision call in the diary from the start, not the end.
- An honest review session with your BA and delivery manager.
- If Parity earns it, a short on-record reference.
After the pilot
Three honest options, agreed before you start.
You will know the terms on day one, so the decision call is about your results, not a sales pitch.
Become a founding partner
For the teams that want to keep going and help shape what we build next.
- A reduced token price, fixed for 12 months.
- A regular session with the founders on the roadmap.
- First access to new features.
- Room for a small number of teams only.
Extend the pilot
If the first two documents were not enough to decide, we agree what else you need to see and how long for.
Stop
We write down what we both learned. You keep the stories Parity created. No follow-up campaign.
Capacity calculator
What is the write-up costing you now?
Put in your own numbers. This uses the same model as our Delivery Capacity Assessment, with nothing hidden. The pilot then replaces our assumptions with your measured ones.
Permanent and regular contractors.
Client or internal, live now.
Adjust the assumptions
BRDs each BA turns into a backlog.
Per document, by hand. Usually 3 to 7.
Contractor or loaded salary.
99 seconds to generate, plus BA review.
Turns days into BA-equivalents.
Turns days into extra projects.
Drives the cost of waiting.
The review figure of 0.5 days is our assumption. Nobody has measured it on your documents yet. The pilot does.
Capacity you could get back each year
432BA days
Waiting 3 months to decide leaves £32,400 of analyst capacity tied up in typing.
Capacity estimates, not cash savings. Recovered time only becomes money when you put it to work: another project, fewer contractors, more time with clients.
How are these estimates calculated?
| Documents a year | Business Analysts × documents per BA per month × 12 | 96 |
| Days spent today | Documents a year × days to write stories today | 480 |
| Days still spent with Parity | Documents a year × days per document with Parity (the review) | 48 |
| Days you get back | Days spent today − days still spent with Parity | 432 |
| Value of that time | Days you get back × BA day rate | £129,600 |
| BA-equivalents | Days you get back ÷ working days per BA year | 2.0 |
| Extra projects | Days you get back ÷ delivery days per project | 7.2 |
| Cost of waiting | Monthly value × months until you decide | £32,400 |
Get started
Apply for a pilot call.
Two minutes. We read every application and reply with times for your 30-minute pilot call. Your two free tokens are unlocked on that call.
Rather talk first? Email parity@crinexglobal.com or book a call.
Straight answers
What people ask before they apply.
Why do I need a call before the free tokens?
Because a pilot nobody has agreed the point of rarely leads anywhere, for you or for us. Thirty minutes to agree the project, the document, what it has to prove and who decides means your two hours count. The tokens are unlocked on that call.
What is a token?
One requirements document through Parity. Upload it, pick your story format, and the epic, stories and acceptance criteria appear on your board. The pilot includes two.
Does this replace our business analysts?
No. Parity writes the first draft. Your BA reviews it, edits it and approves it before anything reaches the board. Refinement, the pre-read and estimation carry on exactly as they do now. Your BA just spends Monday and Tuesday checking stories instead of typing them.
Will it make our developers faster?
No, and we will not claim it does. It changes when the work is ready, not how fast it gets built. What you get is sprints that start with ready work instead of waiting on a write-up.
Can it write in our story format?
Yes. Choose Given / When / Then, As a / I want / So that, or When I / I want to / So I can. The output matches what is already on your board.
Our documents are messy. Will it cope?
That is exactly what we want to find out. Send us the awkward one. If the edge case is written in the document, it should be in the stories. If it only lives in someone's head, your BA adds it in review, same as today.
Where does our document go?
We will send you our security summary before you upload anything, and you are welcome to use an anonymised document for the pilot.
What happens after the pilot?
Nothing, unless you want it to. If it earned its place, you become a founding partner: tokens at a reduced price fixed for 12 months, and a say in what we build next. We share those terms on the pilot call, so there are no surprises at the end.
What if it does not work on our documents?
Then we both know, and that is useful to us. You have spent about two hours and seen exactly where the gaps are.