[ How We Work ]

Six steps. One document. No surprises.

This is the process every Augustova engagement runs on, whether it is a two-week automation or a platform build. It exists in writing because a supplier who will not commit to a method is asking you to carry their risk.

A 30-minute discovery call

You describe the process that hurts. We ask what it costs you, who would sign off a fix, and when you need it working. If we are not the right team for it, we say so on the call and point you somewhere better.

A working prototype, the same week

Not a deck and not a proposal template. We build a working slice of your actual problem and send you a link. You judge us on software, because that is what you are buying.

A fixed price, in writing

One document: the scope, an explicit list of what is not included, the acceptance criteria, the price and the timeline. The not-included list protects you more than it protects us. We do not sell day rates, because a day rate pays a supplier for being slow.

Deposit and data agreement

Work starts after a 50% deposit and, wherever personal data is involved, a signed data processing agreement. Nothing about this step is negotiable, which is exactly what you want from the people about to hold your data.

Build in the open

You see working software at least weekly, not status reports. Decisions that affect scope come to you in writing as they arise, so the final invoice is never a surprise to either side.

A handover that survives us

Documentation, credentials, a runbook, a recorded walkthrough, and training for the people who will use it daily. Code, repositories and provider accounts sit in your name from day one. Two weeks after go-live we review the outcome against the number we agreed at the start.

[ The Standard ]

Four things that are never negotiated

Ownership

Your code, your repositories, your provider accounts, from day one

AI spend

Cost attribution and enforced spending ceilings on every build that calls a model

Data

A signed DPA before any personal data moves, without exception

Support

Agreed in the same document as the build, never negotiated after go-live

[ Common Questions ]

What happens if the build takes longer than you estimated?

Nothing, from your side. The price is fixed against the written scope, so estimating risk sits with us. If you change the scope, the change is priced in writing before it is built.

What do we own at the end?

Everything. The code, the repositories, the provider accounts and the documentation are in your name from day one, and the handover pack means another developer could maintain the system without us.

Do you disappear after handover?

Only if you want us to. A monthly support arrangement is offered in the original proposal so the terms are agreed while you still have full leverage. Either way, the two-week value review happens.

[ Step One ]

The discovery call costs nothing

Thirty minutes, six questions, and an honest answer about whether this is worth building. Even a no leaves you with a clearer scope than you arrived with.

Start a Conversation →