How It Works
Structure, not supervision.
RGC4 automates what can be decided by rule and asks a person only where judgement is genuinely required. That applies to joining the network and to running a project inside it.
The Seven Areas of Work
Every project is described across the same seven areas. Together, we determine which areas apply, why they matter, and what success looks like—so you can see exactly what we heard and correct it.
We start with discovery, then work together to understand the problem, desired outcome, value and readiness.
Usually where we start. Informs every other area throughout.
We work together to define the solution and how it should fit your systems, security, data and existing environment.
Moves back and forth with Build. Revisited when Support feeds back.
Where needed, we build, configure and connect the components required to deliver the solution.
Moves back and forth with Design and with Test.
We validate the solution with your people, data and requirements before it moves into live use.
Moves back and forth with Build, and leads into Deploy.
We help move the solution safely into production, including transition, data movement and cutover where required.
Follows Test, and hands over to Support.
We help the people involved understand the solution and be ready to use it effectively.
Runs alongside Build, Test and Deploy.
We provide the support needed to keep the solution working and help it evolve over time.
Feeds what we learn back into Strategy and Design.
Not every area applies to every project. Areas can run in parallel, and work moves back and forth between them.
Joining the network
Everyone goes through the same qualification, whichever role they apply for.
Choose your role and apply
Five minutes. Sellers, service providers, and customers each have their own path.
An administrator reviews it
A person reads every application. If it looks like a fit, we send a short introduction explaining how the network actually works.
You decide whether to continue
After watching, you tell us yes or no. No is a normal answer and stops all further contact.
Tell us what you do
A short guided profile. Add a resume, case studies, or nothing at all — the system works with whatever you give it, provided it is accurate.
Approval and agreement
If approved, you review and accept the applicable agreement. Only then does a participant record exist.
How an opportunity runs
From a conversation a seller is already having, to a delivered and accepted piece of work.
A seller registers a specific opportunity
One customer, one problem, named contacts, and evidence of a recent conversation. Rules check it; anything they cannot decide is assessed and, if unclear, goes to a person.
The customer describes what they need
Structured intake in the customer's own words. RGC4 turns it into requirements and records their compliance rules — insurance minimums, geography, certifications, data residency.
Delivery partners are filtered, then ranked
The customer's hard requirements are applied literally first. Only providers that pass every one are ranked for fit, and an excluded provider cannot be reintroduced.
RGC4 issues a scope and takes quotes
Providers quote against RGC4's scope. They never see the customer price or each other's quotes.
A proposal is gated before release
Compliance, margin, and legal exceptions are checked. A proposal that fails a gate does not go out until a person resolves the specific blocker.
Delivery is governed, not just watched
The lead practitioner runs the weekly meeting and files a report. RGC4 reads every one and steps in on exception.
Milestones are accepted, then paid
Evidence against every acceptance criterion, then customer acceptance, then payment. Nothing reaches a customer that failed the gate.
What decides what
Anything that can be decided by a rule is decided by a rule, and the rule is published before it is applied to you. Compliance filtering, protection windows, commission, and payment eligibility are ordinary arithmetic — not judgement calls, and not AI.
AI is used where language has to be read: assessing whether a problem statement describes a real problem, whether two registrations are the same opportunity, whether a status report is drifting. It produces a structured recommendation with a confidence, and it is recorded. It never makes a binding decision about anyone’s standing, work, or money.
Where a rule cannot decide and the assessment is not clear enough, a person decides — and that is the only thing the owner is asked to do.