How we work

How a project runs, week by week.

You sign off each step, and you know what you’ll get before it starts.

  • Every weekA demo of working software
  • One senior leadYour contact from first call to handover
  • In writingScope, changes and decisions

From first call to handover

Five steps, each with something to show.

Lengths are typical; your proposal sets the actual plan.

  1. 01

    Discover

    Typical length: 1–2 weeks

    What you get
    • A written brief: goals, users and constraints
    • Risks and open questions
    • A review of your existing code and data
    Who signs off
    You and your lead
  2. 02

    Define

    Typical length: 1–3 weeks

    What you get
    • User flows and wireframes
    • Architecture, data model and API contracts
    • A costed, week-by-week plan
    Who signs off
    Your lead engineer, then you
  3. 03

    Design

    Typical length: 2–4 weeks, overlapping the build

    What you get
    • UI for the agreed screens
    • A clickable prototype
    • A design system that matches the code
    Who signs off
    Your lead designer, then you
  4. 04

    Build

    Typical length: Most of the project; we plan an MVP at 8–14 weeks

    What you get
    • Tested features, merged in small reviewed changes
    • Access to the repository and a staging site
    Who signs off
    A senior engineer approves each change; you accept each milestone
  5. 05

    Launch & grow

    Typical length: 1–2 weeks, then ongoing if you want it

    What you get
    • The release checklist below, completed
    • Monitoring and alerts
    • A handover pack
    Who signs off
    You decide when it goes live

How we keep quality up is on our security & compliance page.

AI tools

AI helps. A person decides.

Faster routine work, same human judgement.

Where they help

Routine work: tests, boilerplate and first drafts of docs.

What a person always does

People make every architecture, security and data decision, and review every change.

Your code and data

AI tools touch your code and data only as your contract allows.

How we handle client data

Who’s on your project

The people and the routine.

Your proposal names the people.

Your lead
A senior engineer or designer who owns the plan and is your day-to-day contact.
Engineers
Write the code; nothing merges without a review.
Designer
Works in the same sprints as the engineers, not a phase ahead.

Stays in your hands

  • The decisions: scope, priorities and what goes live
  • A repository you can see from the first sprint
  • Ownership of the code and designs once the related invoices are paid

Ownership in our Terms

  • Kickoff

    Goals, people, access and the first two weeks, agreed in one session.

  • Weekly demo

    About 30 minutes of working software on a staging site.

  • Weekly update

    Done, next, risks and the decisions we need from you.

  • Handover session

    Your team walks through the code, runbook and accounts with ours.

Ways to work with us

Fixed, monthly, or inside your team.

The right one depends on how settled your scope is.

Fixed project

A defined scope, date and price: an MVP, an app, a website or a brand.

$12k from

Best for
You know what you need and when.
How it starts
An intro call, then a written proposal with scope, plan and price.
Changes
A one-page change note with the cost and time impact; work starts only once you agree.
Billing
A deposit on signing, then by milestone, as our Terms set out.
Get a quote

Join your team

Our engineers or designers work inside your team, repo and rituals.

Quoted after a short call

Best for
You need more hands, or a skill your team doesn’t have yet.
How it starts
We agree the role and first goals with your team lead.
Changes
You set priorities day to day; we own the quality of our work.
Billing
Monthly, with the notice period in your statement of work.
Talk to us

Payments, notice and refunds are in our Terms and Refunds policy.

Release checklist

What we check before launch.

If a check doesn’t apply to your project, we say so in writing before the build starts.

01

Security and access

  • Every API route checks permissions on the server.
  • Admin and staff accounts use two-factor authentication.
  • No keys or passwords live in the repository.
02

Data and privacy

  • Personal data is listed, with where it lives and how long it’s kept.
  • Backups run, and we’ve restored one at least once.
  • Real customer data stays out of test environments.
03

Release and rollback

  • Automated tests run on every change and pass before a release.
  • Every release goes through the same automated pipeline.
  • A bad release can be rolled back in one step, and we’ve tried it.
04

Monitoring

  • Errors are tracked and alert a named person.
  • Uptime checks cover the main user journeys.
  • Logs leave out passwords, tokens and personal data.

Handover pack

What you get at handover.

  • Source code with its full history, and the design files
  • A runbook: deploy, roll back, restore a backup, rotate keys
  • An access list for every account, and how to transfer it
  • A handover session, then our access removed or reduced as you choose

Checklist version 1.1, last reviewed 18 November 2026.

FAQ

Questions about how we work.

Anything else: ask us or email hello@lakemountsystems.com.

Do we have to start with discovery?

Yes, if you already have a clear brief or a product; we still list our assumptions in the proposal.

Who do you need on our side?

One person who can make decisions: at the kickoff, at each weekly demo, and for quick answers in between.

How do you estimate?

We size the scope in small pieces, add time for review, testing and release, and write down the assumptions behind the number.

What happens if the plan slips?

We tell you as soon as we know, with options (cut scope, move the date or add people), and you choose in writing.

Want this plan for your project?