Two of this month's five free Independent AI Audits are still open, included when you start an AI health check.Check eligibility →
Build

The date is fixed, the budget is questioned, and your own team and your suppliers are already full.

Deliver the project that cannot slip: a senior engineer and an agentic team, in control.

If a business-critical mission has a hard go-live date or a challenged budget, bring it to us. A senior engineer who specialises in your domain leads. A team of AI agents does the heavy engineering work. Control, governance and human oversight are built into how the team works, so speed does not cost you assurance.

No obligation. Anything beyond the first discovery session is scoped and priced in writing.

When to call us

Three situations where a different kind of build team pays for itself.

Build is for businesses of ten people or more, and for work that matters to the business.

A date that will not move

A launch, a regulatory deadline, a contract or a board commitment. You need a working first version quickly and a credible route to production.

A budget that has been challenged

The traditional route has been quoted and found too slow or too costly. You want the same quality, delivered with fewer people-hours and clear decision points.

A team that cannot take it on

Your engineers are committed elsewhere and an outsourcing partner needs months to learn your business. You want senior judgement from the first day.

Why this is different

Our agentic team works with control, governance and human oversight built in.

Most fast delivery trades away control. Ours does not. Every agent in the build team has a named human owner, permitted actions and a record of what it did. GenWA Guard checks the work against your rules and the standards you select. The Log records events as they happen, and Evidence turns that record into reports you can show a board, an auditor or a regulator. The GenWA frame holds our best-practice skills and behaviours and loads them into the team, and our harnesses, the controls wrapped around AI so it can work safely, apply them. Senior engineers review and approve what ships.

Hosting in your AWS or Azure account, or hosted by GenWA on AWS as agreed. Control applies to the AI used through GenWA.

The scoping and discovery session

A no-obligation session with a senior engineer, and some of the agentic team.

Meet your engineerA senior GenWA engineer who specialises in your domain joins the call. They listen to the mission, the date, the budget and what has already been tried.
See the agentic team workMembers of the agentic team join to show what GenWA can deliver for you, using your problem as the example, with a human engineer explaining each step and what is checked.
Test the plan against your constraintsTogether we look at scope, risks, hosting, decision points and who on your side approves what. We compare our approach with your internal or outsourced alternative, using your own numbers.
Leave with a written scopeYou receive a short written scope: what we would build first, how the team would be shaped, the controls that apply, and a timeline and price confirmed in writing.
Examples of bespoke projects

Six typical projects: the problem, what we build, and how people stay in control.

Pick the project nearest yours. Each is an example of work we scope with clients, not a fixed product.

Customer relationship management for a software business

The problem

A software-as-a-service business has outgrown spreadsheets and a generic customer relationship management (CRM) tool, and cannot see its accounts, renewals and usage in one place.

What we build

A bespoke CRM built around how you sell, onboard and renew: account and renewal views, usage signals from your product, and workflow automation for the repetitive steps.

How humans stay in control

Your sales and success leads approve the data model and workflow rules. Agents draft and test; senior engineers review; every change is recorded.

See the CRM and content platform

Integrating Amazon Web Services products

The problem

Services in your Amazon Web Services (AWS) account do not talk to each other, or a migration has stalled because nobody has time to wire them together.

What we build

Integration of the AWS products you already use or have chosen, with the connecting code, tests, monitoring and documentation, built inside your AWS account.

How humans stay in control

A named engineer owns the design. Changes pass tests and review before release, and access follows the permissions you set.

Book a scoping session

Setting up a call centre

The problem

You need a contact centre live by a fixed date, with routing, adviser tools and reporting, and not enough time to build it the traditional way.

What we build

A call centre on Amazon Connect, an Amazon product, with call flows, integration to your systems, adviser tools and management reporting. Our Contact product can add adviser assist.

How humans stay in control

Your operations lead approves call flows and scripts. Compliance rules are written down and tested before go-live, and changes need a named approver.

See Contact

A content management system for marketing teams

The problem

Marketing waits on developers for every page, approval is by email, and nobody can say which version of a message went to which customer.

What we build

A content management system (CMS) with templates, approval flows, brand and compliance checks, and publishing to your channels.

How humans stay in control

Nothing is published without an approval from the named owner. The record shows who approved what and when.

See the CRM and content platform

Omni-channel communications with personalised workflows

The problem

Customers hear from you by email, text, chat and phone, and the messages do not follow one story or respect their preferences.

What we build

Workflows that choose the right message, channel and moment for each customer segment, with personalisation rules and one view of every conversation.

How humans stay in control

Messages are drafted against your rules and approved by the content owner. Consequential communications wait for a person.

See Comms

Controls and evidence automation for a regulated business

The problem

You must show regulators, insurers or customers how decisions were made, and the evidence is gathered by hand every time.

What we build

Systems that produce the control record as work happens: events, approvals, exceptions and reports mapped to the rules you select.

How humans stay in control

Compliance defines the rules and approves the reports. We prepare the evidence; accredited bodies issue certification, and this is not legal advice.

See Evidence Packs
How the build team stays under control

Nothing ships without an approval you can see.

Agents prepare and test. Checks run against your rules. A named senior engineer or approver decides what goes forward, and the record is made as the work happens.

Flow from agent work to rules check to named approval to release

  1. 1Document generated

    A record is produced alongside the AI use, as the work happens.

  2. 2Flagged

    Anything that needs a decision is sent to the person who owns it.

  3. 3Approved by a person

    A named person approves, changes or rejects it. AI does not sign off.

  4. 4Recorded

    The decision, the approver and the date are kept with the document.

GenWA Guard and Evidence. Steps shown in order.
Typical projects and what they take

Typical projects and what they take: from a 48-hour emergency proof of concept to multi-million-pound programmes.

Two anchors are firm. Everything between is scoped and priced in writing after discovery, because honest estimates need your scope.

48-hour emergency proof of concept

For a crisis or a decision that cannot wait. A senior engineer and the agentic team show a working proof of the idea in 48 hours. You decide what to do with it. Timeline: 48 hours.

Focused proof of value

A narrow, real use case tested with your data under agreed controls. Team shape: one senior engineer with agents. Decision point: continue, change or stop. Scoped and priced in writing after discovery.

First production release

A working system in front of real users, with tests, monitoring and a handover. Team shape: senior engineer, specialists as needed, agents. Decision points at each release. Scoped and priced in writing after discovery.

Integration and migration

Connecting or moving systems, including AWS products, without stopping the business. Team shape grows with the number of systems. Scoped and priced in writing after discovery.

Multi-team delivery programme

Several workstreams running together, with architecture, governance and reporting to your steering group. Scoped and priced in writing after discovery.

Strategic multi-million-pound programme

A long-running transformation with executive sponsorship, staged funding and independent oversight points. Investment: multi-million pounds. Team and stages agreed in writing after discovery.

Time, quality and cost: how we compare
  • Speed to a working first version
  • Quality and testing
  • Control and governance
  • Human oversight
  • Cost drivers
  • Risk
The typical human-only pattern (internal teams and outsourcing partners)
  • Speed to a working first version
  • Quality and testing
  • Control and governance
  • Human oversight
  • Cost drivers
  • Risk
Human-only teams remain a sound choice for small, well-understood work.

This is GenWA's position, not a measured benchmark. In your scoping session we will show the comparison with your own numbers.

How Build relates to the other ways of working

Build sits alongside the ways we already work with you.

GenWA works in five ways: Advisory, Products, the Incubator, the Accelerator and Build. Build draws on the others and does not replace them.

Who it is for
  • Chief technology officers
  • Chief operating officers
  • Chief executives
    Where it runs and who owns what

    Your code, your cloud, and agreed terms in writing.

    Build work runs in your AWS or Azure account, or hosted by GenWA on AWS as agreed. Agents use approved model providers: OpenAI, Anthropic, Amazon Bedrock, Azure OpenAI, Google Gemini or private models, and personal data is redacted before approved outside model calls. Ownership of code and intellectual property, security terms and exit arrangements are agreed in writing before work begins.

    Control-mapped, not certified. We prepare the evidence; accredited bodies issue certification. This supports compliance and is not legal advice.

    Insights

    Keep reading

    Questions buyers ask

    Straight answers about building with GenWA.

    How fast can you start?

    For an emergency proof of concept, work can begin within days of a scoping session and aims to show a working result in 48 hours. For other projects, start dates and timelines are confirmed in writing after discovery.

    What is a scoping session?

    A free, no-obligation conversation with a senior GenWA engineer who specialises in your domain, joined by members of the agentic team. You leave with a written scope covering what we would build first, how the team would be shaped and the controls that apply.

    Who owns the code and the intellectual property?

    Ownership of code, prompts and the project record is agreed in writing before work begins.

    How are the agents supervised?

    Each agent has a named human owner, permitted actions and a record of its work. Checks run against your rules, and senior engineers approve what ships. Agents prepare and test; people decide.

    Is it secure?

    Work runs in your AWS or Azure account, or hosted by GenWA on AWS as agreed, using approved model providers. Specific security terms are agreed in writing.

    What happens if the project stops?

    You can stop at any decision point. Handover of the work completed, and exit terms, are agreed in writing at the start.

    How do you price?

    The 48-hour emergency proof of concept and multi-million-pound strategic delivery are the two ends of the range. Everything in between is scoped and priced in writing after discovery, so you know the cost before you commit.

    The five ways of working

    The other four ways to work with us.

    Most businesses start with one and add the others. Each has its own page. It is built for businesses with no in-house AI team.

    Bring the mission and the date.

    A scoping session costs you an hour and commits you to nothing.