Scale · Embedded teams and capability transfer

We can't hire senior AI engineers fast enough for our roadmap.

Ambitious roadmaps on real-time, regulated platforms, and not enough senior engineers with AI expertise to deliver them at the pace your market demands.

We embed multidisciplinary teams that hit regulatory and commercial deadlines from the first sprint, work inside your governance rather than around it, and transform your capability from within — so when we step back your own people are AI-ready and the roadmap is still moving. Capability transfer, not dependency.

  • 120+ specialists in 12 embedded squads at FanDuel, maintaining over 95% SLA adherence within regulated frameworks
  • 2 to 5 workstreams scaled within a month at HM Prison and Probation Service, with a sentence calculation engine delivered in three months
  • 65% of our 650 people at senior, lead or principal level, so the people you meet are the people who deliver
  • 100% of our engineers shipping production work with AI tools daily, so every embedded team arrives AI-native

THE PROBLEM

The roadmap is funded. The people are not there.

Capacity problems look simple from the outside. From the inside they are usually about seniority, regulatory exposure and time, not headcount.

  • Hiring takes six months, the deadline is in three

    Senior engineers with real AI expertise and regulated-platform experience are the scarcest people in the market. The roadmap cannot wait for the recruitment funnel.

  • Body shops send bodies

    The last augmentation partner sent CVs, not teams. Onboarding took longer than the engagement, the quality was uneven, and the knowledge left when they did.

  • Real-time, regulated, no room for error

    Peak loads, regulatory deadlines, millions of customers. A team learning the domain on your time is a risk you cannot carry.

  • Dependency instead of capability

    Two years in, the partner is still there and your own teams are no stronger. The spend became permanent and the capability never transferred.

THE PROCESS

Four steps from a capacity gap to an AI-ready team of your own

Embedded teams can be in place within weeks and typically run for six to eighteen months. The Run step is designed in from the first week, because the point is to leave you stronger.

  1. Map

    We match your requirement against our resourcing database — SFIA levels, regulatory exposure, technical capability, sector experience — and shape the squad: product, analysis, architecture, engineering and quality blended for what the roadmap needs. Context packs and technical briefings are prepared before anyone starts.

    You hold: A named, T-shaped squad with the right seniority and domain exposure, ready to start.

  2. Design

    Joint kick-off and a team charter: how the squad plugs into your governance, rituals and tooling, what good looks like, and how capability transfer will work. Weekly delivery touchpoints, monthly reviews and an executive quality board are set up, so engagement health is visible from the start.

    You hold: A squad integrated into your ways of working, with the governance to track it.

  3. Build

    The squad delivers the roadmap inside your business. Regulatory and commercial deadlines are hit, real-time platforms kept stable under peak load, and delivery runs AI-native with Fleet in the lifecycle. Your engineers pair with ours throughout, so the practice transfers while the features ship.

    You hold: Roadmap delivered, deadlines met, and your own people working the AI-native way alongside ours.

  4. Run

    A planned step-back. Knowledge transfer completed, documentation and playbooks handed over, your engineers owning the systems and the practice. Engagement health, velocity and customer satisfaction are reported throughout, and the measure of success is that you need us less.

    You hold: A team that is still yours, working AI-natively, with the roadmap still moving.

THE OUTCOME

Deadlines hit, and a stronger team when we step back

What good looks like:

  • Senior people from the first sprint. T-shaped, multidisciplinary squads with regulated-platform experience, productive from day one.
  • Inside your governance. Working in your rituals, your tooling and your quality boards, not around them.
  • Regulatory and commercial deadlines met. Real-time platforms kept stable, launches made, SLAs held.
  • Capability transferred. Your engineers AI-native and owning the systems, with the practice embedded.
  • Health you can see. Velocity, quality and customer satisfaction reported weekly, monthly and at an executive level.
Three CreateFuture colleagues in conversation on a sofa, one with a laptop open

PARTNERS AND ECOSYSTEM

Teams that arrive certified on the tools you use

Every embedded engineer arrives AI-native: more than 400 GitHub Copilot certifications across our engineering community, 100+ Anthropic-certified practitioners, 750+ OpenAI certifications, and AWS, Azure and Google Cloud depth across the squads.

As part of the Version 1 Group, large programmes can scale beyond our own 650 people through one relationship, with the same leadership and ways of working.

  • Anthropic Preferred Services Partner

    Preferred Services Partner.

    100+ certified practitioners, so the squad that arrives is already working the way your engineers are being asked to learn.

  • OpenAI Select Partner

    Select Partner.

    750+ certifications across our people. Embedded engineers bring the credential and the habit, not just the licence.

  • Version 1 Group

    Scale beyond 650 people.

    Where a programme outgrows us, the same relationship reaches group capacity with the same leadership and ways of working, rather than a second supplier to manage.

BUILT IN-HOUSE, PROVEN ON CLIENT WORK

The accelerator behind this service

  • Fleet

    Coordinates the agents

    An agentic software delivery harness that coordinates coding agents, tools and engineering workflows, with automated quality gates, evaluations and traceability built into production delivery.

    For this work: Embedded squads run Fleet in your delivery lifecycle from the first sprint, so your engineers learn agentic delivery by working inside it — and the harness stays with you when the squad steps back.

See all seven accelerators

LIVE IN BUSINESSES LIKE YOURS

Teams that scaled, and what they delivered

With CreateFuture you get a team that are unafraid to get their hands dirty.

Andy Dunbar

Head of Product and CX, Aberdeen

STILL HUMAN

Leaders who have run 100-person embedded programmes

  • Jules Parry

    Delivery Director

    Owns embedded team engagements and engagement health.

  • Hass Peymani

    Hass Peymani

    Industry Director, iGaming

    Leads the FanDuel, Fanatics and evoke relationships, where our largest embedded teams work.

  • Martin Paton

    Martin Paton

    Chief Technology Officer

    Sets the AI-native engineering standard every squad arrives with.

THE FIRST STEP

Start with one squad and a charter

A one-to-two-week Map shapes a named squad against your roadmap, your regulatory exposure and your tooling, with context packs prepared before anyone starts. The charter says how capability transfer works from the first week, because the measure of success is that you need us less.