Everything FutureAbility does ends in something automated. The work comes in five shapes. Most clients start small and move up; some start at the top. This page sets out what each one is and what you get at the end.
For either kind of agent, or for something that turns out not to need one.
Three weeks, one use case, a small team of ours with a couple of your people. Two questions are answered: can this be built, and should it be. The answers come as working software and a written recommendation.
At the end there is a playback, the written answer to both questions and the evidence behind it. A no is a useful result for three weeks' money. A yes rolls into a First Forward Deployment without paying for the same three weeks again.
A proof of concept is built to be thrown away. Your team does not inherit it, which is what makes three weeks possible.
Usually a process agent, which means someone has to find the process first.
For organisations that already know which process is hurting, this is the usual starting point.
An analyst from FutureAbility works alongside the team that owns the process, with an architect, a developer and a tester behind her. Week one establishes how the job actually runs and what will be measured. Weeks two and three test whether it can be built. At the end of week three there is a stop or go decision. Stop means three weeks paid for and a written reason. Go means the agent is built in your tenant, live at week six, and run by your people for the final two weeks while the measure is tracked.
Fixed price, agreed before the work starts. Where a proof of concept has already covered the first three weeks, the deployment takes five.
Workflows, agents, portals and integrations, usually all in the one build.
Anything larger than a single agent - a portal, a case management system, a records platform, an integration - is delivered as a fixed-price project on FutureAbility's method: Initiate, Implement, Prepare, Operate. The people who scope the work deliver it. Every project ends with twelve weeks of hypercare, because the period after go-live decides whether a system gets used.
You get the system, the documentation, the training and a handover, with support until your people are running it. Some of the work is here.
Prepare to accelerate. The council, the governance and the training that let the next rung happen.
Some organisations need a few things in place before anything is built. Usually that is a group with the authority to decide, and a governance baseline the security team will sign. FutureAbility does four fixed pieces of work here, each with a named output.
Advice on any of this is free in a conversation. Writing it, doing it for you or doing it alongside you is paid work.
Both kinds of agent. This is where the next ones come from.
Once something is live, the question becomes what comes next and who looks after what exists. The Accelerator is a twelve-month retainer that covers both. The apps and agents already built are kept running and improving, and a monthly session with your council weighs the next ideas and moves the best into a proof of concept or a build, with a team that already knows the business. The framework underneath it is written up here.
It is sized to each client: reserved capacity, meeting cadence, and how much of the pipeline work sits with FutureAbility. That is the first conversation.
Prove it, put one live, build the rest, prepare to accelerate, then keep it going. That is the order most clients take. Any rung can be the starting point.
The first conversation is thirty minutes with Tony Brooks. Describe the problem and you will get a straight answer on which of the five fits, or that none does yet.