River~Code
[ About ]

Who you’d be working with.

No mission statement. Here is how the studio is actually set up, what we commit to in writing, and what we won’t take on.

[ How the studio is structured ]

A founder-led studio, honestly described.

River~Code is a small studio. The founder writes the specification and stays on every project from first call to month six, and specialists are brought in per project when the work genuinely needs them — working to the same written scope you do.

Small is deliberate rather than temporary: it is what makes a fixed price possible and what stops your project being handed to whoever is free. You always know who is doing the work.

[ Time zones ]

How we work across the day.

US, UK & EU overlap
Support hours cover all three business days. A question sent during your working day is answered during your working day, not overnight.
One business day
Everything gets a reply inside it — including the messages that are just questions.
[ How we work with clients ]

Six terms, and they are all in writing.

  1. 01

    Fixed price and fixed date, before anything starts

    Agreed in writing. If the build runs over, that is ours to absorb.

  2. 02

    A written scope, with exclusions and a definition of done

    Including what is explicitly out of scope, and the price of a change request.

  3. 03

    Support hours overlapping US, UK and EU business hours

    Stated as a working window, so you know when you can reach us.

  4. 04

    You own everything we build

    Code, workflows, accounts, credentials — entirely, from day one, in writing.

  5. 05

    We say no to work that needs a second technology stack

    If a project would require you to migrate systems, we have scoped it wrong, and we will tell you rather than take it.

  6. 06

    We maintain what we build

    Monthly, on a retainer. Most automation projects die at handover. Ours starts there.

[ How we scope ]

What we will tell you before you pay.

We would rather lose a project at the quote than deliver one that was scoped wrong.

  • If the automation would not pay for itself, we say so — that is what the Roadmap is for.
  • If a job would mean replacing software you already pay for, we will scope around it or tell you the honest cost of not doing so.
  • We quote fixed price, not hourly. If the work cannot be scoped, it cannot be quoted, and we will say that too.
  • If your confidentiality requirements are stricter than the terms below, we will tell you before you sign, not after.
[ Data and documents ]

Where your documents actually go.

We build with AI tools, which means some project content passes through third-party AI providers as part of development. We say that before anyone asks, and it is the reason we don’t offer a formal NDA — signing one would be promising a standard of confidentiality the build process doesn’t meet.

What we do commit to, in writing: we never disclose that we work with you, never discuss your business, and never share your documents or data with anyone outside the project. If your compliance requirements are stricter than that, this is where you find out — before signing, not after.

Find out where the money is leaking.

The Automation Roadmap maps your process, counts the manual steps and prices the fix. Two weeks, $1,200.

We reply within one business day.