Why not use our own team?

Your own team may be the best choice. We assess that during the sprint. A separate team can help when the venture needs to test a product before your platform roadmap or release schedule allows.

What does the sprint commit us to?

You commit only to the sprint. You can use its scope, architecture, risk assessment and estimate with your internal team, with us or with another supplier.

What happens to our IP and data?

They remain yours. We follow your infrastructure and security requirements. We agree data-processing terms and intellectual property assignment before the sprint starts.

What if it works and we want to bring it in-house?

We plan for that handover. We document the architecture, provide tests and work with your team so they can take over development and operation.

For corporate venture teams

Test a new product outside your platform roadmap.

We define the scope and estimate the work for your venture. If you choose to work with us, we deliver a first production version that your internal team can take over.

See what the sprint delivers

The scope explains the estimate.

Your internal team has to account for uptime, compliance, shared services and scheduled releases. Its estimate includes the work needed to protect the systems other teams depend on.

A new venture needs to test whether customers want the product before the business commits to further investment. That first version may need fewer features than a full platform integration.

A smaller scope and agreed technical constraints may allow a separate team to build it. That estimate covers different work from the platform estimate.

We help you compare the scope, cost and risks of each approach so you can decide which one supports the business case.

Before development

Start with an independent scope and estimate.

The technical strategy sprint takes one to two weeks for a fixed fee. We examine the venture assumptions, define the first version needed to test customer demand and agree the technical constraints with your IT team.

You receive the proposed scope, architecture and integration boundaries. We document the risks and assumptions, and explain the delivery estimate so you can use it in the business case.

We may recommend your internal team, our team, another supplier or stopping the project. The sprint does not commit you to a development contract.

Discuss your venture

Decide separately on planning, development and handover.

You review the result of each phase before agreeing to the next.

1. Define the scope and estimate

We check the platform, security, data and procurement requirements. We propose a scope and explain its cost, risks and assumptions.

2. Build with a separate team

If you choose external development, we build against the agreed plan. We use specifications and AI-assisted development, with automated checks, code review and senior approval of changes.

3. Hand over or keep support

We document the system and work with your team on development and releases before they take over. If you want ongoing technical leadership, we agree that separately.

How we use AI in development

Prepare for your team to take over.

We agree how your organisation will approve, operate and maintain the product before development starts.

Involve IT and security early

During the sprint, we agree cloud hosting, identity management, data boundaries, standards and review requirements with your team.

Ownership in the contract

The contract assigns the code, intellectual property, infrastructure, accounts and documentation to you.

Documented architecture

We use established approaches and document the system so developers outside the original team can maintain it.

Defined terms for procurement

The first phase has a fixed fee and defined deliverables. Our company can sign your framework agreement and confidentiality agreement.

An agreed handover

We agree what to hand over, who needs to take part and when the transition will happen.

Reference projects and handover work

Vigiler and ASK@ROUND show our work on a live financial application and a mobile product released on iOS and Android.

Replacing the Vigiler financial platform

We redesigned and rewrote the web and mobile product while the existing service continued to process transactions. We prepared the internal team to develop and release the new software through documentation, a development starter kit and pairing sessions.

Read the Vigiler case study →

Releasing ASK@ROUND on iOS and Android

We built the iOS and Android application with one Flutter codebase, its Firebase services and automated release pipelines.

Read the ASK@ROUND case study →

Questions about working with us

Why not use our own team?: Your own team may be the best choice. We assess that during the sprint. A separate team can help when the venture needs to test a product before your platform roadmap or release schedule allows.
What does the sprint commit us to?: You commit only to the sprint. You can use its scope, architecture, risk assessment and estimate with your internal team, with us or with another supplier.
What happens to our IP and data?: They remain yours. We follow your infrastructure and security requirements. We agree data-processing terms and intellectual property assignment before the sprint starts.
What if it works and we want to bring it in-house?: We plan for that handover. We document the architecture, provide tests and work with your team so they can take over development and operation.

Tell us about the product you want to test.

We'll review the idea and your technical constraints, then discuss whether a separate development project would fit your budget and timing.

Discuss your venture