GROMAGROH-muh
System Blueprint
The groma was the Roman instrument used to lay out cities before they were built. Our Blueprint lays out your system the same way.
A buildable, priceable plan, with acceptance criteria you sign.
Is this for you?
- Initiatives ready to scope after a Diagnostic
- Teams that need a fixed price they can trust
- Projects where several systems and departments are involved
The situation
Several systems, several teams, and no shared plan yet.
Your initiative has outgrown a single workflow. It touches more than one system, more than one department, and records that different teams each treat as the truth.
At this stage, every open question turns into contingency in someone’s estimate. Nobody has yet written down what the system must do, which rules it follows, or how anyone will know it works.
What you need is a plan your team can read, a builder can price, and your approver can sign. The question is what exactly to build, and what it will cost to build it well.
Our approach
Design the system, then agree how it will be accepted.
The Blueprint starts from your operations: the workflow, its constraints, and the records each step depends on. We name the systems of record, the business rules, and the line between what agents prepare and what people approve.
Every outcome then goes into the Acceptance Charter with its test, threshold, test data, and the person who runs it. You sign the Charter before any build begins, so the definition of done is settled in writing.
The build is then priced against that Charter, as a fixed price or an hourly plan. You see the scope, what sits outside it, and the basis of the price before you commit.
Use cases by industry
Where this service fits.
Typical applications across industries. They show where the service applies, not past client work or results.
- Credit union
Member loan files prepared across departments
The Blueprint maps how a member loan file moves from application through underwriting to closing, across lending, operations, and member service. It names the authoritative record for each document and the rules each department applies. Agents would assemble and check the file, a loan officer approves every lending decision, and the Charter defines how completeness is tested.
- Manufacturer
Quotes prepared from drawings and costing rules
The Blueprint traces how quotes are built from customer drawings, material costs, routing times, and shop capacity. It records the costing rules estimators apply, including the ones held only in memory, and where each figure lives in the ERP. Agents would prepare draft quotes, and an estimator approves each quote before it reaches the customer.
- Logistics
Delayed shipments handled across carriers and customers
The Blueprint designs a system that follows shipment status across the transportation management system, carrier updates, and the commitments made to each customer. It defines which record is authoritative when those sources disagree, and who may change it. Agents would draft customer notices and rebooking options, and a dispatcher approves every change before it is committed.
- Clinic group
Referral intake across several clinic locations
The Blueprint maps how referrals arrive at each location, how eligibility and urgency are checked, and how appointments are offered. It sets the boundary around sensitive records and names who may read or change each one. Agents would prepare intake summaries for staff, and front-office staff approve each booking and every message to a patient.
- Engineering consultancy
Project setup from signed proposal to kickoff
The Blueprint follows a new project from signed proposal into project accounting, the document library, and the staffing plan. It records the rules for project codes, budgets, rates, and team assignments that each office applies. Agents would prepare the setup records, and the project manager approves each one before any time is billed against it.
- Hospitality
Group booking requests across sales and operations
The Blueprint maps group requests from first inquiry through contract, rooming lists, and event orders, across the sales and operations teams. It names the property management system and the sales records as the source of truth for each step. Agents would draft proposals and event orders, and the sales manager approves every commitment on rates or space.
- Real estate brokerage
Transaction files checked from offer to closing
The Blueprint designs how transaction documents are collected, checked, and tracked against each contract deadline from offer to closing. It records the brokerage’s file review rules and the owner of each checklist item. Agents would check documents for missing signatures, initials, and dates, and the transaction coordinator approves every file before the broker signs off.
- Energy services
Field inspections turned into customer proposals
The Blueprint connects field inspection data, equipment records, incentive rules, and pricing into one path to a customer proposal. It defines which system holds each fact, how conflicts are resolved, and who owns each rule. Agents would draft proposals from inspection findings, and a sales engineer approves each proposal and its pricing before it is released.
What you receive
Architecture and boundaries
The system design, what agents do, what people approve, and where the source of truth lives.
Business logic and data model
The rules the system must follow and the records it reads and writes.
The Acceptance Charter
Each outcome with its test, threshold, test data, and who runs it, signed before any build starts.
A fixed price or an hourly plan
The build priced against the Charter, with a schedule.
How it works
- DiscoverMap the workflow, constraints, and authoritative records.
- DesignSpecify boundaries, business rules, and system interfaces.
- Define acceptanceAgree tests, thresholds, and the people who evaluate them.
- Approve the planYour owner signs off on architecture, scope, and delivery.
How success is measured
The measures your approver signs.
Each measure goes into the acceptance criteria with its test data, threshold, and the person who checks it.
- Workflow coverage
- Each workflow in scope is mapped from start to finish. The owner of each one reviews the map and confirms it matches how the work runs.
- A source of truth for every record
- Every record the system reads or writes has one authoritative system and a named owner. The check is a walk through the data model with your system owners.
- Approval points defined
- Every point where an agent hands work to a person is named, with the approver’s role. Your approver confirms each boundary before the Charter is signed.
- Charter completeness
- Each outcome in the Acceptance Charter has a test, a threshold, test data, and a named evaluator. Any outcome missing one of these is completed before signature.
- A traceable price
- Each part of the price traces to scope in the Charter, and items outside scope are listed. The basis of the price can be checked line by line.
Where care is needed
What we watch, and how it is handled.
- Unwritten rules
- Many operating rules live in people’s habits rather than documents. We capture them in working sessions, and the people who apply them confirm each one.
- Conflicting records
- Teams often hold different copies of the same fact. The Blueprint settles which system is authoritative on paper, before any code exists.
- Scope that grows
- Initiatives tend to widen during planning. Each addition goes into the Charter with its own test or onto a list for later, and your approver decides which.
- Agent boundaries
- An agent’s reach is set by the records it may read and write. The Blueprint names those limits and the person who approves each action beyond them.
- A plan others can build from
- The Blueprint is written so any capable engineering team can read and price it. Whoever builds, the signed Charter measures the result.
Who does what
Your team decides. We engineer.
Your team
- Name an approver who can sign the architecture and the Charter
- Bring the owners of each workflow and system in scope
- Share documentation, exports, and system access as agreed
- Confirm the business rules, including the ones nobody wrote down
- Choose the pricing basis and decide whether to build
Sophrono
- Map the workflows, records, and handoffs with your teams
- Design the architecture, boundaries, and human approval points
- Document the business logic and the data model
- Draft the Acceptance Charter with you for signature
- Price the build against the Charter, fixed or hourly
At the end
The decisions you make next.
The service ends with evidence and a choice. Each option is yours, and none is assumed.
Build the full system
Commission Custom Agentic Systems to build against the signed Charter, at the agreed fixed price or under the hourly plan. The Charter defines when the system is accepted.
Pilot one workflow first
Choose the workflow with the clearest owner and run a Production Pilot under production conditions. Its results inform the full build.
Strengthen the foundations
When rules or records need work first, the Business Logic Registry or System-of-Record Architecture prepares them for the build.
Hand it to your team
Your engineers build from the Blueprint, and the signed Charter remains the test of done. The rules and data model give them a shared reference throughout.
Before we start
What to have ready.
- A short description of the initiative and the outcome it serves
- The systems involved, and the person who owns each one
- Any process maps, policies, or rule documents, however rough
- Findings from a Diagnostic or a workload evaluation, if you have them
- The person who will sign the Charter and approve the plan
Related services
What “accepted” means
Measured against criteria you agree to in advance.
- Every in-scope workflow has a documented system boundary.
- Each outcome has an agreed test and named evaluator.
- The plan identifies authoritative records and permission owners.
- Your approver accepts the architecture and delivery scope.
Full engagement terms are finalized in a Master Services Agreement.
See a sample Acceptance CharterRequest a proposal
Tell us what the system should do.
We reply with the questions that shape scope, then a proposal with the fee agreed before work begins.
- A senior engineer reads every request
- A reply by email with the next step
- No obligation until scope and price are agreed
Not ready to scope this? Ask an engineer first: a free 15-minute call that names the agentic systems that could fit.
The Canon rule behind this service
System Blueprint answers to Canon I.
Free template
See exactly what “accepted” means.
The sample Acceptance Charter shows how every outcome gets a test, a threshold, test data, and an owner before a build begins.
- Criteria written as tests
- A clear acceptance window
- Change orders for new criteria
Sample Acceptance Charter
Preview it firstWhere this fits
- Learn Research
- Explore free AI Workload Evaluation
- Try one workflow Diagnostic
- Plan and validate System Blueprint
- Build Custom Agentic Systems
- Improve and operate AI Stewardship
Not ready yet? Agentic Engineering Diagnostic. After this: Production Pilot or Custom Agentic Systems.
Questions
Is this the same as the Agentic AI Blueprint?
No. The Agentic AI Blueprint is a one-page plan for one workflow, included with the $750 Diagnostic. The System Blueprint designs the whole system and its acceptance criteria, as its own scoped engagement.
What if the Blueprint says not to build?
Then it has done its job. You learn that before paying for a build, and the plan still records what you would need later.
How is the scoping deposit handled?
The deposit is credited toward the agreed fee. Restrictions apply, and they are set out with the deposit before work begins. Full engagement terms are finalized in a Master Services Agreement.
Who owns the plan?
Ownership is set out in the Master Services Agreement, alongside the other engagement terms.
Can the Charter change after it is signed?
Yes, by agreement. The approver signs each change, written into the Charter with its own test. Any effect on the price is agreed at the same time.
How do we choose between a fixed price and an hourly plan?
A fixed price suits a scope the Charter pins down closely. An hourly plan suits work where some discovery continues during the build.
Can our own engineers build from the Blueprint?
The plan is written to be read and priced by engineers, including your own. Who builds is your decision, and the Charter measures the result either way.
Does the Blueprint cover permissions and security?
It identifies the authoritative records and who owns permission to change them. Security requirements that shape the architecture are recorded alongside the boundaries.
How is the Blueprint itself priced?
It begins with a scoping deposit, which is credited toward the agreed fee. Restrictions apply. The scope and fee are agreed before work begins, so the cost of planning is known up front.
Do we need a Diagnostic first?
No. A Diagnostic helps when you want to see one workflow behave in code first. An initiative that is already well understood can start with a Blueprint.
What if our teams disagree about how the work runs?
That is useful to learn before the build. We record each version, the owners agree one, and the approver settles anything left open.
Where do agents fit in the design?
Where agents suit the work, the Blueprint defines what each one prepares and which records it may touch. A named person approves every action that commits the business.
Can the design keep systems we already use?
Yes. Existing systems are mapped as they are, with their records and owners. The design works around them, and any change to them is listed in scope.
Can we pause after the Blueprint?
Yes. The decision to build is separate from the plan. The signed Charter and the price give you what you need to decide when the timing suits.
How detailed is the Acceptance Charter?
Each outcome has its test, threshold, test data, and the person who runs it. That detail lets anyone check the finished system against what was agreed.
What do our teams need to give the work?
Time in working sessions with the people who run each workflow, and access to documentation and exports as agreed. Their confirmation of the rules is what makes the plan reliable.
Can the Blueprint cover only part of an initiative?
Yes. Scope is agreed before work begins, so the Blueprint can cover the systems and teams that matter first. Anything left out is listed for later planning.