How we work
Come with a problem, not a spec.
The best systems come from understanding the business, not from transcribing a wish list.
Every engagement follows the same six steps: a short first meeting, an NDA, a working draft built in a few days at no cost, then a fixed-price build, a security assessment, and a documented go-live.
The journey
Six steps, no surprises
Before you commit
Nothing owed- 01
A short first meeting
An hour, in person or on a call. You give us the overview of the problem and the business; we ask a lot of questions. That's all it takes to start.
- 02
NDA, then the detail
We put a mutual NDA in place first, then you share the business-specific information: the spreadsheets, the systems, how the work actually flows and where it hurts. Don't hold back — the more context we have, the better the first build.
- 03
The draft build — at no cost
We go away and build a working draft in a few days. You see your own process running, not a proposal. If it's not right, you walk away owing nothing. If it is, we agree the full build.
The full build
- 04
Development build
We build the platform properly on a fixed scope and a fixed price: the data model, the integrations, the screens, the workflows — iterating with you as it takes shape.
- 05
Stop and take stock: security
Before anything goes live we pause and bring in our CISO consultants to assess the data-security needs of your business: what data the platform holds, UK GDPR obligations, whether you hold or are working towards ISO 27001 or Cyber Essentials, and any industry-specific requirements such as DSPT for health and social care.
- 06
Secure, document, go live
We work in partnership with you to put the relevant documentation and processes in place — data-handling, access control, retention, incident response — and confirm the platform's data handling is secure. Then we go live, with a written security statement you can show your own customers.
Don't hold back.
It starts with a short first meeting and an NDA, and after that the single biggest factor in whether a build succeeds is how much context we get. How the business actually runs, what the data is, where it lives, when things happen and why. Which problems keep coming back. Which reports get built by hand every Monday.
So we ask one question early: if anything were possible, what would the ideal look like? What is the best possible outcome for your business?
Most people have learned to be cautious with requirements, because every extra line used to come with a price tag. That has changed. If there is a way to reach the data, we can build what you actually need and present it the way you want it — and, honestly, it will probably be better than you imagined.
Bring us the problem, the wish list and the spreadsheets. We'll tell you what's realistic, and it is usually more than you expect.
Come prepared with
The problem
What is slow, manual, error-prone or invisible today.
The context
How, what, where, when and why the work happens, and where the data lives.
The ideal
If anything were possible, what would you want to see, and how would you want to see it.
“VeriTrend began as a first meeting with a care provider. The ambient-voice analytics platform only appeared because we dug into the business problem rather than the brief.”
FAQ
Common questions
Is the first version really free?
- Yes. After a short first meeting and an NDA, we build a working draft in a few days at no cost. If it isn't right, you walk away owing nothing. If it is, we agree the full build at a fixed scope and price.
Why do you ask for an NDA before the detail?
- Because the draft only works if we understand how your business actually runs, and that means seeing real processes and data. The NDA is in place before any of that is shared.
Why is there a separate security stage?
- Before anything goes live we stop and bring in our CISO consultants to assess what data the system holds, your UK GDPR obligations, whether you hold or are working towards ISO 27001 or Cyber Essentials, and any sector-specific requirements such as DSPT. Then we put the documentation and processes in place and go live with a written security statement.
How long does a build take?
- A draft in days; a fixed-price Spark build in two to four weeks; larger platforms are scoped and quoted after the draft.
Ready to start with a first meeting?
No spec required. An hour of your time, then an NDA and the detail.