Before access
Agree the records, environments and permitted uses. Establish provider restrictions, data handling and the relevant technical, privacy and security owners.
Working together
A clear start.
A shared way forward.
Work directly with Form From to investigate, build and integrate a capability your organisation needs. We agree the first decision to resolve, the evidence it needs and how we will work with your team.
The first conversation
Bring the context.
We’ll help frame the question.
You may have an operational problem, an existing AI initiative or a broad mandate to explore what is possible. Tell us who does the work, which systems it touches and what you would like to change.
We’ll discuss whether we are a fit and what needs to be understood before proposing a scope. A high-level description is enough; access to sensitive records can be arranged when it is needed.
The first commitment
Match the engagement
to the uncertainty.
We choose a starting point with you and define its deliverables, dependencies and review points. Each option should leave you better able to decide what happens next.
Working session / Find a worthwhile opportunity
Bring business and technical perspectives together to examine a workflow, surface constraints and prioritise a question. You receive an opportunity brief with the proposed first test, owners and unresolved requirements.
Technical assessment / Understand an existing system
Review an agreed part of the application, architecture, model workflow or delivery process. You receive findings, supporting evidence and a prioritised recommendation. Any formal security or compliance assurance needs its own agreed scope.
Feasibility test / Resolve a specific unknown
Test whether an approach meets a defined quality, integration or operating requirement using representative tasks and an agreed data boundary. You receive results, limitations and a recommendation to proceed, revise or stop.
Engineering engagement / Deliver a defined capability
Build or improve the agreed application, integration or AI workflow. You receive working software, acceptance evidence and the documentation and handover specified for the engagement.
A workshop does not commit you to a pilot. A successful test does not automatically become a production release. Further work follows an explicit decision.
Working as one team
Use your delivery process.
Strengthen the team around it.
We can work in your repositories, with your issue tracking, CI/CD and existing suppliers. Our research infrastructure and engineering tools support the engagement where they fit; adopting our internal platform is not a prerequisite.
Form From leads the agreed research and engineering. Your team supplies operational knowledge, appropriate access and a nominated decision-maker. Together we review working software, test results and unresolved questions.
Capability transfer can be part of delivery: working on real tickets with your team, improving task specifications, reviewing AI-generated changes and building the judgement to continue the work.
Engineering and review
Make accelerated delivery
reviewable.
Our AI-assisted engineering practice separates implementation, review and integration. Changes are scoped, committed and checked against agreed behaviour. Failed attempts and repair rounds remain part of the evidence.
We agree a review cadence and show the implications when findings change the scope, timing or approach. The people responsible for release retain the decision to put changes into use.
Explore the delivery practiceGovernance in delivery
Know who needs to approve it.
Know what they need to see.
During evaluation
Test permissions, source evidence, approval steps and failure behaviour alongside the task. Record performance and operating cost under the conditions tested.
Before release
Confirm acceptance, approvals, monitoring and recovery. Name the owners of access, updates and support before people depend on the system.
Delivery and handover
The system. The evidence.
The ability to continue.
The agreement sets out ownership, code access and third-party dependencies. Handover includes the agreed software, evaluation record, operating documentation and responsibilities. Support and further development have an explicit scope.
Can you join an existing programme?
Yes. We can take responsibility for a defined piece of research or engineering, work alongside your internal team, or coordinate with existing suppliers. We agree interfaces, decision rights and review points at the outset.
Who will lead the work?
Nahele Allan-Moon, Founder and CTO, leads Form From’s technical direction. The delivery lead, contributors and availability are identified for the engagement before work begins.
Can we start without choosing a model or hosting provider?
Yes. Model selection and deployment can be questions for the initial assessment. Your organisation’s requirements and the task determine the options to evaluate.
Who supports the software afterwards?
Your team, an existing provider or Form From can take on defined responsibilities. We agree this before release, including maintenance, updates and how issues will be handled.
Let’s make it work
Let’s establish the next useful step.
Tell us what is known, what is uncertain and who needs to make the decision. We’ll help shape a first commitment you can assess.
Start a conversation