01 · The portal
One place where your team can see what’s happening and the partners you approve send work in and keep it updated — under your brand, on your own domain. An engine keeps it all moving behind them, and the red assistant answers questions from whatever each person is allowed to see.
Shaped around how you already work · configured, never re-coded
Next actions
What it replaces
Most things that go wrong here aren’t decisions gone wrong. They’re things that quietly waited. One system takes the place of the inbox, the spreadsheet and the shared drive that hold the work between them today.
Dashboard
Everyone lands on a screen that answers the same five questions: what needs attention today, what changed, what to do next, what’s blocked, and what’s mine. Nobody has to assemble that picture out of three tabs and a phone call.
Portal
Your team and the partners you approve log in at your own address. Your logo, your colours, your labels. No red-route hostname ever appears in a partner’s browser — we’re the engine room, never the storefront.
red
Ask in plain language and get an answer drawn from what that person is already allowed to see. It runs on our own hardware, and the conversation’s gone the moment they log out.
Engine
Acknowledging what arrives, routing it, moving statuses, chasing what’s missing, reminding, flagging. It’s the difference between a system that files the work and one that moves it along.
Your partners
Every partner sees their own work and nothing else, which is the only reason you can safely hand a login to an organisation you don’t employ. They log in at your address, under your name.
Partner portal
Northgate Advice
Only your organisation’s submissions
No red-route address ever appears here.
The portal, its forms and everything behind them sit under your domain. You point one DNS record at us; you never run hosting, a server or a certificate yourself.
Logo, colours and the label on the front door come from your configuration. A charity and a roofing firm run the same platform and share no visual DNA.
The portal serves your organisation and the partners you approve — never your own end customers or the public. The only pages a stranger can reach are the forms you deliberately publish. Because everyone else is a known name, access can be strict rather than merely convenient.
The assistant
Nobody has to learn where a figure lives, or build a report to find it. They just ask. The red assistant answers from what that person is already allowed to see, and nothing else.
The lookup runs on our server against your own database, filtered to the person asking, before the model sees anything. It isn’t trimming a big answer down. It never had the rest.
The red assistant runs on a model on hardware we run. If that model’s unavailable it says so and stops. There’s no graceful failover to a cloud AI, because that would put your data somewhere it must never go.
Questions, answers and transcripts aren’t written to your tables, to browser storage, or to our logs. Close the tab, switch role or log out and the conversation’s gone.
The assistant won’t surface or summarise anything on a protected path, whatever it’s asked. That path stays separate however the question is worded.
Session only · nothing stored · never sent to a third-party AI
The engine
Fewer things missed, less chasing, faster handovers. It does the parts of the job that are only ever admin, and it does them at three in the morning if that’s when they land.
Activity log
0 people involved · 0 items waiting for morning
Whatever arrives is logged the moment it lands, stamped with a status, and acknowledged. Nobody has to be watching an inbox — a referral that arrives at 9pm is on the board before anyone has read it.
Nobody has to remember to chase it. Anything incomplete gets followed up on the schedule you set, so a quote waiting on a decision or a job sheet missing a signature doesn’t stall for a week because the person who noticed went on holiday.
When something moves, the people who need to know are told. Overdue work gets chased. Anything at risk shows up on a screen instead of sitting in one person’s head.
Automations are configured per client, not copied per client. Yours reach your database and no other, and a change you ask for lands in days rather than joining a release queue.
Roles
Three roles, renamed into your language when we set you up. In a charity they’re a referrer and a delivery centre; in a roofing firm, a customer contact and a subcontractor. The labels change; the boundaries don’t.
Sees everything the organisation is doing: work in progress, partner activity, approvals, outcomes and anything flagged. Every decision inside the portal belongs to this role.
Sees only what they sent in. Submits new work through a guided form, then follows where each one has got to. Never sees another partner’s.
Sees only the work assigned to them. Marks progress, submits outcomes, and raises a concern down its own separate path.
red-route staff hold no operational authority inside your portal. We provision, host and maintain the platform — approvals, status changes and every operational decision belong to your own admin.
Shapes
We build your portal from a kit we’ve built before, starting from whichever of these is closest to how you already work.
Someone refers a person in, you match them to a provider, and everyone can see how it went afterwards. Anything protected stays on its own path.
Cases with an owner, a status, a risk level and an obvious next action, so nothing sits unowned.
An enquiry becomes a survey, a survey becomes a priced quote, and an accepted quote becomes a job in the diary.
Built for a phone in one hand: what this job needs, ticked off step by step, with buttons big enough to hit in the rain.
What is in, what it is worth, what has gone quiet, what is stuck, and how the month is going.
Boundaries
Not settings, and not a tier. They hold for every client on every plan, whether or not anyone thinks to ask.
A partner sees their own work and nothing else. It’s enforced on our server against who they logged in as, never by hiding rows in the browser, so a curious partner can’t reach anyone else’s by trying.
Anything that needs a stricter path gets its own route, its own workflow and its own separate storage. Never mixed into another list, never in an export, and the assistant never surfaces it.
Inside the portal, people entitled to see a name see it. Anything that leaves — an email, an export, a PDF — carries a reference instead.
No permanent login, no password stored in the browser, no conversation history. Close the tab and the session’s gone.
Tell us where things get stuck today and we’ll show you the console your team would land on, and what we’d take off them.