One or two people hold it all
What the contract requires is understood by whoever read it. Everyone else asks them, waits, or guesses — and when they are on leave, the practice guesses.
For GP practices, PCNs and federations
Everyone in your practice can answer contract questions. Not just the person who read it.
InBrief reads your service specifications and turns them into answers your whole team can use — with the passage each one came from shown alongside it. No patient data. No clinical advice. Nothing sent without a person approving it.
Half an hour, against a specification you already hold. Twelve-week paid pilots from £500.
- Hours, not daysA specification read, structured and searchable in the time it takes to make coffee.
- One source of truthApproved once, used by everyone — reception to the management team.
- Every answer checkableThe passage behind it is one click away, so nobody has to take it on faith.
- Nothing lost when someone leavesContract knowledge stays with the organisation, not with the person who read it.
Used by the people who have to read the specification and then make it happen — practice managers, PCN managers, service leads, care coordinators and reception teams.
The specification nobody has time to read
Dozens of pages. The obligations, the indicators, the deadlines and the payment conditions are spread through all of them — and the people who have to act on them are not the people who read them.
The same letter, written again
Patient communications get redrafted from scratch by whoever is free, slightly differently every time, at whatever reading level they happen to write at.
Nobody notices the contract changed
A specification is reissued and the team carries on working from last year's, because the differences are on page thirty-one and nobody has time to diff two PDFs.
What using it actually looks like
Four screens, in the order you meet them. These are real screenshots of the product, with invented data.
Upload
Put the specification in
A contract, a service specification, or approved organisational information. It is read, segmented and checked before anything else happens.
Review
See what it found, and where
Obligations, indicators, deadlines, eligibility rules and payment terms, each one linked to the passage it came from.
Approve
A named person signs it off
Approved items become what the organisation relies on. Anyone can then ask a question in plain English and see the source behind the answer.
Use
Turn it into something a patient can read
Letters, texts and leaflets drafted from approved content at a chosen reading level, with your practice details already in them.
What your team gets
Four capabilities, all working from documents your organisation has approved.
Contract knowledge that outlives the reader
- Obligations, KPIs, deadlines, eligibility rules and payment arrangements, extracted.
- Every item linked back to the passage it came from.
- Approved once, and kept as the organisation's source of truth.
- A reissued contract sits alongside the old one rather than quietly replacing it.
Answers without interrupting anyone
- Staff ask in plain English and get an answer from approved documents.
- The supporting passage is shown, so the answer can be checked.
- Usable from reception, not just by the management team.
- An answer that cannot be grounded is refused rather than guessed.
Patient communications, drafted consistently
- Letters, SMS, emails, leaflets and appointment guides at a chosen reading level.
- Why the patient is being contacted, and what happens next.
- Your practice's own details inserted automatically.
- Translation into the languages your population actually speaks.
Nothing quietly out of date
- A reissued contract is uploaded against the same document, not over it.
- Previous versions stay readable, so you can see what changed.
- Each extraction stays attached to the version it was made from — an item approved last year does not start claiming to describe this year's contract.
- Retention is configurable, and deleting a document deletes the files too.
Built for people who have to justify the decision
Every line below is enforced in the software, not written for the website. The detail — data handling, tenant separation, audit, retention, model usage — is on the security page.
No patient-identifiable data
Not a policy — a refusal. Uploads are scanned and rejected if they look like they contain patient identifiers.
No clinical advice
No diagnosis, no triage, no treatment recommendations. That boundary is what keeps InBrief outside the medical device regime.
A source on every item
An item that cannot be traced back to a passage is discarded. The database will not store one without a citation.
A person approves
Nothing a patient would read gets there without someone with the right to approve it having done so, under their name.
History cannot be rewritten
Reviews, approvals and the audit log are append-only, enforced in the database rather than by convention.
One tenant cannot see another
Row-level security on every table holding customer content, forced, through a role that cannot bypass it.
Encrypted, and yours to delete
HTTPS throughout, encryption at rest, and a delete that removes every version and the stored files — not just the index.
Not used to train a model
Your documents go to the model that reads them, and are not training data for us or for the model provider.
See it working
The whole product, with invented data, in its own tab. Nothing to install and nothing to sign up for.
Interactive demonstration — fictional example data only
The whole interface, at full size, in its own tab. Look through a contract breakdown, ask a question, draft a patient letter and translate one. No account, no sign-up, nothing to install.
Open the interactive demo (opens in a new tab)No information is uploaded, stored, sent or retrieved from live systems in the demonstration. The practices and contracts in it are invented.
What we can show you today
InBrief is early, and we are not going to put invented quotes on this page. Until there are pilot customers willing to be named, here is what you can check for yourself instead.
Use the whole product
The interactive demonstration is the real interface with invented data — not a slideshow, not a lead-capture form. Open it and look for what it cannot do.
Open the demoTest it on your own contract
A demonstration takes half an hour and uses a specification you actually hold, so you see what it finds and what it misses rather than an example we chose.
Book oneRead how it handles your data
Tenant separation, audit, retention, deletion and model usage, written for the person assembling a DPIA rather than for a brochure.
Security and governanceBuilt by someone who has delivered NHS services
Louis Williams founded InBrief after several years in NHS primary care operations and transformation — managing contracts, service specifications and performance across GP practices and PCNs. The problem was always the same: too much operational knowledge locked in long documents, or held by a handful of experienced people.
Pricing
Per practice. Unlimited staff accounts on both plans, because charging per seat would keep the contract knowledge with the people who already have it.
Annual billing works out lower per month — Core is £66 a month rather than £79.
InBrief Core
£790 per practice / year
£66 a month, billed annually
- Unlimited staff accounts
- Unlimited document uploads, under fair use
- Contract and specification analysis
- Ask InBrief, with a source citation on every answer
- Patient communication generation
- Practice-specific details applied automatically
- 60 translation units per practice each year
- Standard support
Recommended
InBrief Plus
£1,090 per practice / year
£91 a month, billed annually
Everything in Core, plus
- 240 translation units per practice each year
- One human-reviewed translation credit per practice each year
- Priority support
All prices exclude VAT.
Buying as a PCN
Practices buying together
| Practices | Discount |
|---|---|
| 2 | 10% |
| 3 | 15% |
| 4 | 20% |
| 5 | 30% |
| 6 | 30% |
| 7 or more | Priced individually |
Paid pilot
- One practice, 12 weeks — £500
- A PCN, up to six practices, 12 weeks — £1,000
The pilot fee is credited against an annual subscription if you convert within 30 days of it ending.
Founding customer
Limited availability
- 20% subscription discount
- Assisted onboarding included
- Annual commitment
- Structured product feedback
- Agreed case-study participation
A fixed cohort rather than a standing offer. When it is full it closes.
Expert support, when you want it
Delivered by people and quoted per engagement, for when a contract needs more than reading. The software works on its own.
- Contract Assurance Review
- Performance Improvement Strategy
- Mobilisation Sprint
- KPI and Reporting Setup
- Patient Communication Review
- Funding Application Review
- Funding Bid Sprint
- Partnership Support
- Service Delivery Health Check
Also expert consultation and advisory retainers. All quoted per engagement.
See all servicesWhere the product stops
What InBrief does
- Works only from documents your organisation has approved.
- Shows the passage behind every answer and every extracted item.
- Puts review and approval in front of anything a patient would read.
- Keeps an append-only record of who approved what, and when.
What it does not do
- Send anything to a patient. There is no send route, and no messaging gateway.
- Give clinical advice, diagnose, or triage.
- Hold patient-identifiable data, or connect to a clinical system.
- Tell you which of your patients are outstanding on anything.
- Decide anything on your behalf. A person approves what the organisation relies on.
These are boundaries, not gaps waiting to be filled. Several of them are what keep InBrief outside the medical device regime. InBrief is not affiliated with or endorsed by the NHS.
Questions we get asked
The ones that decide whether a procurement conversation happens. Answered from what the software does, not from what would sell well.
Can InBrief see our patient records?
No. It has no connection to EMIS, SystmOne or any clinical system, and no integration is planned that would give it one. It reads the documents you upload and nothing else.
Should we upload anything with patient details in it?
No — and it tries not to let you. Every upload is scanned before it is processed, and one that appears to contain patient-identifiable data is rejected with the reason, rather than quietly accepted. Contracts and service specifications do not contain patient data, so this should never fire in normal use.
Are our documents used to train an AI model?
No. Your documents are sent to the model that reads them and are not used as training data by us or by the model provider.
How do we know an answer is not invented?
Every extracted item carries a citation to the passage it came from, and the interface shows you that passage. An item the system cannot trace back to the document is discarded rather than displayed — the database will not store one without a source. Answers to questions are drawn from the approved documents and quote them.
What happens when a contract is reissued?
Upload the new version against the same document. Previous versions stay readable, and each extraction stays attached to the version it was actually made from, so an item approved last year does not silently start claiming to describe this year's contract.
Can different practices see different documents?
Separate organisations cannot see each other's documents at all — that is enforced in the database rather than in application code, so a query that forgot to filter would still return nothing. Within one organisation, staff share the document library, and what differs is what each role may do: extract, draft communications, approve translations, manage settings.
Can we control what staff can do?
Yes. Eight roles, each with its own combination of four rights, enforced on the server rather than by hiding buttons. A receptionist can read the answers and cannot start an extraction or approve a communication.
What can we upload?
PDFs, up to 32MB each. A scanned PDF with no text layer is detected and reported rather than silently producing nothing.
Does InBrief send anything to patients?
No. It drafts communications for a named person to approve, and there is no send route and no messaging gateway in the product — approved text leaves as an export, and whatever you already use to contact patients sends it.
Are translations checked by a person?
A translation has to be approved by someone with the right to approve it before it can be used, and the approval is recorded against their name. Independent linguistic review by a qualified translator is available as a paid service where a communication warrants it.
Can we get our documents back, and can they be deleted?
Yes to both. Extracted items export to CSV, and deleting a document removes every version, its extractions and the stored files — which is what makes an erasure request actually erase something.
Where is our data held, and can we see a DPA?
Ask us and we will answer precisely, in writing, for the arrangement you would actually be on. We would rather tell you than publish something that stops being true when the infrastructure changes.
See it against your own contract.
A demonstration takes half an hour. A paid pilot runs twelve weeks and starts at £500, credited against an annual subscription if you convert.