Skip to content

How we work

From your brief to the last pull request

What happens after you send a brief: who you talk to, what you sign, how the work is done and how it reaches you. Questions first? Message us on WhatsApp.

How does a project work?

  1. Brief

    Six short steps at /start. Attach designs and specs, and ask for an NDA first if you need one.

  2. Scope

    We read every brief ourselves, ask what’s missing, and send a proposal with the scope, the rate and the dates.

  3. Sign

    An NDA, a master services agreement and a statement of work, signed online with a code sent to your email.

  4. Build

    Background agents work on the tasks in parallel, each in its own sandbox. A senior engineer reviews every change.

  5. Deliver

    Every change reaches you as a pull request in your repository, and each invoice comes with a summary of the work and the time.

Why build with background agents?

We build with Open-Inspect, an open-source system of background coding agents (MIT). It’s how a small studio works on many tasks at once without cutting corners.

  • Work in parallel

    Agents take independent tasks at the same time, each in a full development environment, so a feature doesn’t wait in a queue.

  • Every change reviewed

    Nothing merges because an agent wrote it: a senior engineer reviews each pull request before it reaches you.

  • Your repository, your history

    The work lands as pull requests you can read, comment on and merge, with every commit in your history.

  • The right model for the task

    Open-Inspect runs Claude, OpenAI Codex and other models, so each task gets the one that does it best.

Which contracts will you sign?

Our own templates, the same for every client, so you can read them before you start. Ask for any of them in your brief.

  • Mutual NDA

    Before you share details, if you ask for one

    Both sides keep each other’s information confidential while we discuss your project. Tick “I need an NDA” in your brief and we send it before asking for anything confidential.

  • Master services agreement

    Once, before the first project

    The terms every project shares: payment, warranty, who owns the work, confidentiality and liability.

  • Statement of work

    One per project

    The objective, the scope, the rate (by the hour, the day or the month), the estimate if there is one, and the dates. An estimate is never a fixed price, and we ask before going past an agreed cap.

  • Data processing agreement

    If the work touches personal data

    GDPR article 28 terms, with the EU standard contractual clauses, for work that handles your users’ personal data.

  • Change order

    If the scope, the dates or the fee change

    A signed change to a statement of work, so what we build and what you pay never drift apart.

  • Acceptance certificate

    At delivery

    Records that the work is delivered and starts the acceptance period.

How does signing work?

  1. We prepare the contract from our template and send it from our CRM.
  2. Latitude 10 signs first.
  3. You get an email with a link, open the contract, and sign after entering a code we send to your email.
  4. Both sides get the signed PDF, and we keep a copy with the contract.

Signing runs through eSignatures.com. Nothing to install and no account to create.

Who owns the code?

You do, once the work is paid in full. It runs on your infrastructure, in your repository. The kit code inside it stays ours and is licensed to you, for good, for that project.

What it costs: by the hour, the day or the month.