Services

Three services, bought one stage at a time.

They run in order, but you do not have to buy them in order. Most engagements start with the first and stop when the system is running; some begin halfway, because the decision is already made. Each stage is scoped and priced before it starts, and you can stop at the end of any of them.

01 / Decide

AI Strategy & Roadmap

Find the handful of problems where AI changes your economics, size the value, and sequence them into a plan your board will fund.

What this covers

Opportunity assessmentBusiness caseOperating modelGovernance & risk

What you get

  • Ranked use-case portfolio with value and feasibility scores
  • Business case for the top three use cases
  • 12-month sequenced roadmap
  • Governance framework and risk register

02 / Ship

Build & Deploy

Engineer the thing into production inside your systems — with evaluations, guardrails and monitoring — not a demo that dies after the steering committee.

What this covers

Prototype to productionAgentic workflowsData & retrieval foundationsEvaluation & observability

What you get

  • Production system running in your environment
  • Evaluation suite and quality baseline
  • Monitoring, alerting and rollback plan
  • Handover documentation and code your team owns

03 / Embed

Adoption & Enablement

Make the system part of how people actually work — training, workflow redesign and internal champions — so value shows up in the numbers, not just the pilot.

Typically Ongoing

What this covers

Workflow redesignEnablement programmeInternal capabilityChange measurement

What you get

  • Redesigned workflow documentation
  • Role-based training and enablement materials
  • Adoption dashboard with agreed metrics
  • Capability plan and transition to your team

Delivery

The same method behind every service

Whichever stage you start at, the work runs through the same four steps, each ending in something you can look at and judge for yourself.

The full method
Step 01

Discover

Find the problems worth solving and rank them by value and feasibility.

You getPrioritised use cases and a business case

Step 02

Prove

Build the riskiest part first, on real data, and measure it against a baseline.

You getWorking prototype with evaluation results

Step 03

Build

Engineer it into your systems with monitoring, guardrails and a human in the loop.

You getProduction system your team can run

Step 04

Scale

Train the people, redesign the workflow, and extend to the next use case.

You getAdoption metrics and a roadmap for what comes next

Questions

Before you get in touch

If yours is not answered here, ask it — dj@visiongen.io reaches the people who would do the work.

How does an engagement start?
With the Starting Point Review: one working session with the people who would own the system, spent ranking what you are considering and scoping the first thing worth building. You leave with that shortlist whether or not we work together. If you decide to go on, the first stage picks up from exactly where the session left off.
How long until something is in production?
The first working version comes out of the Prove stage, built on your real data; a production system follows at the end of Build. What moves that date is almost never the modelling — it is how quickly we get access to real data, how many systems it has to talk to, and how fast decisions get made on your side. We will give you a dated plan at the end of Discover, once we have seen those three things rather than guessed at them.
Will this work with our existing data and tools?
We build inside your environment and on your stack rather than beside it, which is what makes handover possible at the end. What we need from you is access to the real data, one person who knows how the process actually works today, and someone who can make a decision without convening a committee. If the data is not ready, Discover will say so plainly instead of quietly building around it.
How do you handle security and data privacy?
Your data stays in your environment wherever the work allows it, and where it cannot, we agree in writing what moves, where it is processed and when it is deleted before anything moves. We ask for the least access that lets us do the job, granted through your process and revoked at the end of each stage. We will sign your DPA, work to your security policy, and assign the IP in everything we build to you.
Who will we actually work with?
The people in the first conversation are the people who build the thing. We are small and senior on purpose: no pyramid, no handover to a team you have not met, and no junior learning on your budget. You will know exactly who is on your engagement, and what they have shipped before, prior to committing to anything.
How is pricing structured?
Each stage is scoped and priced before it starts, so you are agreeing to one stage at a time rather than to a programme. You can stop at the end of any of them and keep everything produced to that point, including the code. We do not work on open-ended retainers, because an engagement that cannot end is not the same thing as one that succeeds.

Next step

Have a problem worth solving?

You will hear back within a working day, from the person who would do the work rather than someone selling it. If we are not the right firm for what you need, we will say so and tell you who is.