GIUNTURA

Small steps, each one paid for and tried before the next.

No hourly meter and no long wait before you see something. The price is agreed first, the work is split into parts you can open and use, and everything runs on accounts in your name.

Start a project

The five stages

  1. 1

    Brief

    What happens
    You describe the problem in your own words, in writing. We ask questions back until we can repeat it to you correctly.
    What you get
    A plain answer, including when the answer is that this is not work we should take.
    What we need from you
    What is in the way today, who it slows down, and any date you are working towards.
  2. 2

    Scope and fixed price

    What happens
    A small, clear job gets a one-page proposal: the problem, what we build, the price, the time. Anything bigger or still open starts with a paid discovery that ends in a written scope with a fixed price for each milestone.
    What you get
    A one-page proposal, or a discovery document you own even if you stop there.
    What we need from you
    One person who can decide, and access to whatever we have to read to price it honestly.
  3. 3

    Paid per milestone

    What happens
    A milestone is at most about two weeks of work, and it is paid before it starts. That keeps the most you ever have at risk down to one milestone.
    What you get
    A written definition of done for the milestone you are paying for. For AI work that definition is a set of test cases, because the same question does not always get the same answer.
    What we need from you
    Payment for the milestone before it begins.
  4. 4

    Build and preview

    What happens
    We build in the open: written updates as we go, and a short recorded video at each milestone showing the thing actually running.
    What you get
    Something you can open and use at the end of every milestone, not a status report.
    What we need from you
    Your comments on each preview, and a decision when we ask for one. Anything new that comes up gets its own price before we build it.
  5. 5

    Launch and look after

    What happens
    We release under accounts in your name, hand over the code and the notes, and fix bugs for 30 days after handover.
    What you get
    The running product, the source code, and instructions the next developer can follow.
    What we need from you
    A decision on whether you want a monthly plan. Both app stores raise their requirements every year, and an app that misses a deadline cannot be updated until it catches up.

How pricing works

You know the price before any work starts. Which model applies depends on how clear the job already is.

From $50

Small, clear jobs

One fixed price, written down before we start, paid up front.

Usually done within a week

From $500

Bigger projects

A paid discovery first, then a fixed price for each milestone, each one paid before it is built.

Each milestone is at most about two weeks of work

From $200 a month

Monthly plan

A fixed amount of work each month, agreed before the month starts.

Runs month by month, stop whenever you like

True in all three

  • Rights to the code move to you once each milestone is paid.
  • Apps, servers and store listings stay on accounts in your name.
  • Anything outside the agreed scope gets its own price, and you decide before we start it.

Who this suits

We would rather say so now than three weeks in.

A good fit if

  • Someone else built your app or your system, and it still needs work.
  • You want the price agreed before anything starts, not a meter running.
  • You want to put something small in front of real users, then decide the rest from what they do.
  • You want the person who wrote the code to answer your questions.

Probably not if

  • You need a team starting next week.
  • You want to be billed by the hour.
  • You want building to start before the scope is written down.
  • You need someone in your office.

Questions about how we work

What does a paid discovery cost?

It is priced like any small, clear job, from $50, and it ends in a document you own: the scope, the milestones and a fixed price for each. If you want the fee treated differently should you continue with us, say so at the start and we will put that in writing.

What if a milestone is not what I expected?

We agree what done means before the milestone starts, so there is something specific to point at. If the work does not meet it, fixing that is part of the milestone, not a new charge. Because milestones are small and paid one at a time, the most you ever have at risk is one of them.

Who owns the code?

You do. Rights to the code move to you as each milestone is paid, and the app, the servers and the store listings live on accounts in your name. We ask to be invited with limited access, never for the account owner's password.

What if the scope changes halfway?

New work is new work. It gets its own price in writing, and you decide before we start it. Nothing outside the agreed scope gets built quietly and billed later.

What happens after launch?

You get the code and the written instructions, and bugs are fixed for 30 days after handover. After that you can keep us on a monthly plan from $200 a month, or hand everything to another developer. The accounts are already yours, so nothing has to be untangled first.

Who pays for AI and tool subscriptions?

You do, on your own accounts, so you see the usage and nothing stops if we part ways. For AI work we agree on test cases up front, and done means passing them.

How do we stay in touch?

Mostly in writing, with a short recorded video at each milestone. Calls are scheduled ahead with an agenda.

Tell us what you're building.

A few sentences is enough. We'll reply with questions or a next step.