Start a project

Software you can see working every week.

A London software company. We design, build and run web platforms, apps and AI features, with a working demo every week and code you own from day one.

  • London in London
  • Battersea, London
  • Company No. 16876520
  • Founded 2025

Most projects go quiet. Ours don’t.

Most software projects go quiet somewhere between the kickoff and the launch. Weeks pass, the budget moves, and nobody can show you what works yet. We run projects the other way round: a fixed-price discovery, a demo every week and code in your repository from the first day. You always know what you have paid for, because you can open it and use it.

Discovery
2 weeks, fixed price
Demos
Every Friday
Code
Yours from the first commit
First reply
Within one working day

Five days, and something you can click on the fifth.

  1. Monday

    Priorities

    A short call to agree what matters this week. You decide the order; we tell you honestly what fits.

    Monday, the priorities call.
  2. Tuesday

    Build

    Engineers work in your repository. Every change is reviewed by a second person before it is merged.

    Tuesday, two engineers on one change.
  3. Wednesday

    Check-in

    A written note on progress and anything that needs your decision, so nothing waits until Friday.

    Wednesday, sorting what needs your decision.
  4. Thursday

    Test

    Automated tests run on every change, and we try the week’s work on real phones and browsers.

    Thursday, the flow checked screen by screen.
  5. Friday

    Demo

    You click through working software, not slides. Notes and next week’s plan arrive the same afternoon.

    Friday, the demo.

Discovery first. Then a demo every week.

Discovery is a fixed price and ends with a written plan you keep. Everything after it is planned with you, in weeks you can see.

  1. Discovery

    2 weeks, fixed price

    Workshops, a technical review and a written plan with scope, risks and a cost range. You keep the plan whether or not we build it.

  2. Design

    2 to 4 weeks

    Flows and screens tested with real users. Architecture agreed before the first sprint.

  3. Build

    Two-week sprints

    A demo every week. Code in your repository from day one. Priorities set by you at every sprint.

  4. Launch

    Staged release

    Release to a small group first, then everyone. Monitoring and rollback ready before the switch.

  5. Run

    Monthly

    Support, fixes and improvements on a monthly plan, or a clean handover to your own team.

Three ways to work with us.

Fixed-scope project

A clear product or feature with a defined finish line.

  • Fixed price per phase
  • Discovery first
  • Typical length 2 to 6 months

Dedicated team

Ongoing product work where priorities change month to month.

  • Monthly rate per person
  • Senior engineers and a lead
  • One month notice

AI sprint

You want to know if an AI idea works before you fund it.

  • Four weeks
  • Working prototype on your data
  • Accuracy and cost report

Built to a standard you can check.

Written into every proposal. Ask for the evidence at any Friday demo.

  1. Security

    Every release goes through dependency checks and the OWASP Top 10 basics. Secrets live in a vault, access follows least privilege, and backups are restored in practice, not just taken.

    • Dependency and secret scanning on every merge
    • Least-privilege access, reviewed every quarter
    • Restores tested, not only backups taken
  2. Performance

    Pages load quickly on a mid-range phone on an ordinary connection. We set a weight budget for each page before design starts and check Core Web Vitals on real devices.

    • Largest content visible in under 2.5 s on mobile
    • No layout shift while loading
    • A weight budget for every template
  3. Accessibility

    Built to WCAG 2.2 AA from the first component, and tested with a keyboard and a screen reader, not only with an automated scan.

    • Keyboard and screen reader tested
    • Contrast and focus states checked
    • Reduced motion respected
  4. Data protection

    UK GDPR is part of the first workshop. We collect only what the product needs, write down where it lives and agree how long it is kept.

    • Data map and retention periods agreed
    • Access to personal data logged
    • Every processor named in the contract
  5. Handover

    Any project we build can be picked up by another team. Tests, runbooks and architecture notes are part of the work, not an extra at the end.

    • Automated tests run in the pipeline
    • Runbooks and architecture notes kept current
    • A recorded handover session

What a project with us looks like.

Three typical projects, described the way we would scope them. They are examples of the work, not named clients.

A UK homeware retailerIllustrative example

Search by photo across 40,000 products

Customers photograph a lamp they like and see similar items in stock, ranked by price and delivery time.

  • AI & computer vision
  • Web & mobile apps

A regional courierIllustrative example

Delivery paperwork read in seconds

Drivers photograph signed delivery notes. Fields are extracted, checked and posted to the billing system the same day.

  • AI & computer vision
  • Custom software
  • Data & analytics

A UK creator platformIllustrative example

A credit ledger that survives refunds

Users top up credits, spend them per action and get paid for their sales. Every movement is recorded, so balances, refunds and payouts always reconcile.

  • Custom software
  • Cloud & DevOps
  • Data & analytics

Where our work is most at home.

  • Retail & e-commerce

    Visual search, product tagging, catalogue tools and checkouts that convert.

  • Fintech & payments

    Ledgers, credits, payouts and the checks that keep regulators comfortable.

  • Media & creative

    Image generation, asset libraries, rights management and creator marketplaces.

  • Logistics

    Reading paperwork, tracking parcels and tools for the people on the road.

  • Property

    Listings, viewings, document handling and portals for tenants and landlords.

  • Professional services

    Client portals, document search and internal tools for firms that bill by the hour.

Six things we do the same way every time.

  • You own the code

    From the first commit, in your repository, under your account.

  • Demos, not decks

    Every week you see working software, not a status slide.

  • One contract, English law

    A UK company, a UK contract and a named person responsible for your project.

  • Senior people do the work

    The people in the first meeting are the people who build your product.

  • Discovery at a fixed price

    Two weeks, one price, a plan you keep either way.

  • Honest about AI

    If a simple rule beats a model, we will say so and build the rule.

Questions we hear most often.

How much does a project cost?

It depends on scope, so we start with a two-week discovery at a fixed price. You get a written plan with a cost range before committing to the build.

How quickly can you start?

Discovery can usually start within two weeks of the first call.

Do you work with companies outside the UK?

Yes. We work in English, mostly in UK hours, with clients across the UK and Europe.

Can you take over a project from another supplier?

Yes. We begin with a short code and infrastructure audit and tell you plainly what we find.

Do you sign NDAs?

Yes, before the first detailed conversation if you prefer.

What happens after launch?

You choose: a monthly support plan with us, or a documented handover to your own team.

Tell us what you are building.

A short call, a clear next step. We reply within one working day.