River~Code
[ Operations automation for agencies ]

Your account managers are doing admin, not accounts.

River~Code builds the onboarding, reporting and intake systems that give billable hours back to the people who should be billing them. Fixed price and a fixed date, agreed in writing before we start.

How work moves before and after an automation system On the left, forty jobs in a month, each carried by hand through the same chain of steps across separate inboxes, spreadsheets and drives. Several stop dead and are dropped. On the right, all of the surviving work arrives at one system, from which a single automated workflow runs continuously without anyone carrying it. Every step by hand Fifteen steps ✕ Client signs Workspace created
How work moves before and after an automation system On the left, jobs carried by hand through the same chain of steps, several stopping dead. On the right, all the surviving work on one automated workflow that runs continuously. Every step by hand Client signs

[ What we automate ]

  1. 01

    Client onboarding & workspace setup

    The system that stops it happening again.
  2. 02

    Reporting automation

    Read, checked and filed without anyone retyping.
  3. 03

    Lead routing & scope tracking

    Assembled and sent without anyone remembering to.

… and plenty of other systems. These are the three we get asked for most.

[ Sound familiar ]

Your account managers are doing data entry.

  • Onboarding a new client means the same fifteen manual steps, every time.
  • Monthly reports assembled by hand from four dashboards.
  • Leads arrive in a form and someone copies them into the CRM.
  • Your most expensive people spend their week on work you can’t invoice.

An account manager on $60k spending eight hours a week on admin costs you roughly $12,000 a year in time you could have billed.

[ What changes ]

From nine manual steps to one system that runs itself.

Nothing changes about how your team works. It runs behind them.

Now — carried by a person
  1. 01Client signs
  2. 02Slack channel created
  3. 03People invited
  4. 04Drive folders copied
  5. 05Project created in the PM tool
  6. 06Ad, analytics and CMS access requested
  7. 07Access chased again
  8. 08Kick-off doc and dashboard built by hand
  9. 09Team briefed

9 manual steps

After — runs by itself
  1. 01Client signs
  2. 02Workspace created
  3. 03Access granted
  4. 04Kick-off doc generated
  5. 05Reporting connected
  6. 06Team notified

1 workflow

[ Examples ]

Some of what we automate.

Client Onboarding System

A new client onboarded in minutes, not a day.

  • Workspace & folder creation
  • Access provisioning
  • Kick-off document generation
  • Reporting connected
  • Team notified

Reporting Automation

Monthly client reports assembled from your existing dashboards, on schedule, without an account manager doing it by hand.

  • Dashboard connections
  • Scheduled assembly
  • Branded output
  • Delivery to the client
  • Exception flagging

Lead & Enquiry Routing

Leads out of the form and into the CRM without anyone copying them across.

  • Form capture
  • Deduplication
  • CRM creation
  • Owner assignment
  • Follow-up sequence

Retainer & Scope Tracking

What was sold against what is being delivered, before it turns into an awkward conversation.

  • Scope logged at sale
  • Delivery tracked against it
  • Overrun flagged early
  • Renewal reminders

These are examples, not a menu. If the thing eating your week isn’t here, describe it — the Roadmap exists to work out whether it’s worth automating.

[ How it runs ]

How a build runs.

Three phases — and you have the price and the date in writing before the first one starts.

01

Map

Access, process mapping, specification signed off. You know exactly what’s being built, and what it costs, before anything is built.

02

Build

We build it, and you see it running on your own data — not a status report, not a demo environment. The thing itself, working, while there’s still time to change it.

03

Hand over

Testing on live data, training your team, a recorded walkthrough and a written runbook. Then we keep it running — handover is where we start, not where we finish.

[ How long does it take ]

One workflow is usually about three weeks. Bigger systems get split into stages, and every stage carries its own fixed price and its own date — so scope grows in steps you agreed to, not in an invoice you didn’t expect.

[ Every proposal includes ]
  • What’s in scope
  • What’s explicitly out of scope
  • The definition of done
  • Two rounds of revisions
  • The price of a change request

All five, in writing, before you pay anything. This is our answer to “we tried this before and it didn’t stick.”

[ Proof ]

Systems we’ve actually built.

A few examples of real projects we’ve delivered. What each one replaced:

Built for iC Consulenten

Time tracking & payroll

Before
Everyone kept their hours in Excel. At month end somebody added them up by hand, per person and per project, then worked out leave separately.
After
Hours are logged as the work happens. Totals per person and per project, reports and leave balances all come out of the system — nobody re-enters anything.

Running today

Built for CES Clean Energy Solutions

Compliance assessment

Before
Each client’s environmental assessment was worked through by hand in a spreadsheet, by someone who knew the rules, one client at a time.
After
The client’s data goes in, the assessment runs itself, and the result comes back in a form the business can act on and take into a client conversation.

Running today

Built on Microsoft Power Automate

Mail & attachment routing

Before
Attachments arrived by email and were opened, renamed and filed into the right folder by hand, every time.
After
Mail is sorted and attachments filed on arrival, on the Microsoft tools the company already paid for.

Running today

[ What’s left ]

Questions we get asked.

What if my team won’t use it?

They won’t have to. It runs in the background. If your team has to change how they work, we’ve built it wrong.

Do we have to replace our software?

No. We connect what you already have and fill the gaps between it. If a project requires you to migrate systems, we’ve scoped it wrong.

Who maintains it?

We do, monthly. That’s the actual product, and it’s why the retainer exists.

We could build this ourselves.

You probably could. The question is whether the person who’d build it has three spare weeks — and whether it gets maintained after they move onto a client project. Time is usually the constraint, not capability.

Does it work with our reporting stack?

If the dashboards have an API or scheduled exports, yes. We connect what you already pay for rather than moving you onto something new.

What if you disappear?

You own everything we build: code, workflows, accounts, credentials. Everything is documented in a runbook at handover. Another developer could pick it up.

Where does my data go, and can you sign an NDA?

We use AI tools as part of how we build, so some project content passes through third-party AI providers as part of the development process — we won’t pretend otherwise, and it means we can’t offer the kind of absolute confidentiality a formal NDA implies.

What we do commit to, in writing: we never disclose that we work with you, discuss your business, or share your documents or data with anyone outside the project. If your work requires a stricter data-handling standard than that, tell us before we start and we’ll tell you honestly whether we’re the right fit.

Do I own what you build?

Yes. Entirely, from day one, in writing.

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.