Book a call

Working with us

Start with a project, keep us on, or let us look after it.

Most clients start with a defined project, then keep us on to grow the product or to run it once it’s live. Pick the line below that sounds like you.

Working with SprintX

Where are you right now?

Pick the line that sounds like you.

We’d suggest

A defined project

A new system, an AI agent, or a model trained for one job.

  • Agreed scope and budget before we start
  • A demo of working software every week
  • You own the code and the docs

AI pilots from $5,000

Scope a project

The first weeks

Four steps, the same on every project.

  1. 01

    Map the work

    We sit with the people who do the work today and map the process as it actually runs.

  2. 02

    Measure the baseline

    Time, errors and cost for the task as it is now, written down before we build anything.

  3. 03

    Build in small releases

    Working software early, reviewed with you as it develops.

  4. 04

    Report the same numbers

    After launch we measure the same things again, so the result is a number, not an opinion.

How we work

Intake, building, feedback and bugs.

What happens at each stage, so you know what to expect before you start.

Intake

How a project starts

  1. 1Tell us what you’re trying to fix, by form, email or a 30-minute call.
  2. 2You talk to the people who would build it, not a sales team.
  3. 3We send a written scope: what we’ll build, what we won’t, the cost and the timeline. No work starts before you agree it.
  4. 4Kick-off: access, one shared channel and the first week planned.

Building

Week to week

  1. 1One shared channel with the team doing the work.
  2. 2A demo of working software every week.
  3. 3A task board you can open any time.
  4. 4Code lives in your repository from day one.

Feedback

How changes get decided

  1. 1Comment on the demo build; we keep every note in one list.
  2. 2Each change is confirmed before we build it: inside the scope, or a change with its cost and time.
  3. 3Nothing is called done until you’ve seen it working.

Bugs

When something breaks

  1. 1Report it with Crosscheck, our one-click bug reporter: it attaches the screen recording, console and network logs.
  2. 2We sort it the same working day. Critical means down, data or payments; everything else is normal.
  3. 3Fixed, tested and shown to you, with a check added so it doesn’t come back.
  4. 4Reply times for each level are agreed in your plan.

Work

A few of the projects behind this.

All case studies

Care retainer

Once it’s live, we keep it healthy.

Every plan is agreed per product. Each month you get a health report you can read in ten minutes: what we promised, what happened, and what needs your decision.

A typical plan covers

  • Uptime monitoring and alerts, around the clock
  • Daily backups, kept off-site, with restore tests
  • Security updates and a regular security check
  • Bug fixes
  • A set number of development hours each month
  • Agreed reply times for normal and critical issues
  • A monthly health report

Questions

Before we start.

  • Yes. You get calls with the engineers on your project.