Satoris.build × West Park · Product Roadmap
Building the platform,
block by block.
A fluid, agile partnership — not a big-bang project. Each cycle we ship a
block that saves the team time today and becomes the foundation the next block stands on.
Shipped
Ship-now
Compounding
Maturing
The principle
Power without overwhelm.
The risk
Every feature is a tax
Another button. Another screen. Another thing to learn.
Add enough and the platform that was meant to save time starts costing it.
The discipline
- Automate the spine — add power by removing steps in the work itself.
- Personalize per role — add clarity by showing each person only their slice.
- AI removes steps, it never adds screens. Every AI feature must take clicks away.
The model
Two axes.
Every initiative is one, the other, or both — power down the spine, clarity across roles.
Automate the spine — power ↑
PM
Buyer
QS
Director
Estimate
Budget
Procurement
PM sees only
his project's POs
Site
Performance
Personalize per role — clarity →
One platform, three views
Three lenses, three audiences.
Lens 01 · the build
The spine
What flows: estimate → budget → procurement → site → performance. How we build.
Lens 02 · the experience
The roles
Who sees what: PM, buyer, QS, director. How the team lives in it daily.
Lens 03 · the investment
The domains
Logistics · financials · performance · payroll · agents. How the owner funds & reads it.
We build along the spine, the team
experiences it by role, the owner funds and reports it by domain — same work, three angles.
The spine
Everything connects to the job.
01 Estimate
Estimating agent
02 Budget
Variations from budget
Material schedule pre-load
03 Procurement
Price-list call-offs
PO time slots
PO version history
Deliveries on the Gantt
04 Site
On-site discipline
PM logistics loop
05 Performance
PM scorecards
All-role scorecards
ShippedShip-now
CompoundingMaturing
Domain in focus · Logistics
From call-off to delivery,
in one line of sight.
↓ notifies buyer
▤
Buyer raises
Purchase order · delivery date + time slot
↓ plots automatically
▦
On the project Gantt
Material arrival, against the programme
↓ reconciles
£
Lands against the PO
Invoice — PM kept in the loop
- Material arrivals plotted on the Gantt — the gap today; PM sees deliveries against the schedule.
- Delivery time slots on every PO, not just a date.
- Notified at each handoff → visibility becomes accountability.
The calm layer
Same data, the right slice.
RoleProject manager
- His projects only
- Call-offs he raised
- His POs & invoices
- On-site checklist & margin
RoleBuyer
- Cross-project command
- All call-offs → POs
- Supplier price lists
- Deliveries pipeline
RoleQuantity surveyor
- Cost vs budget
- Variations
- Margin movement
- Valuations
RoleDirector
- Portfolio financials
- Aging & risk
- The AI digest
- Performance overview
Each person logs into only their world — the platform
can hold enormous capability precisely because no one has to see all of it.
The multiplier
Agents sit on top of
every domain.
Not a silo — a layer. One agent can serve logistics, financials, or performance.
Phase 0 · shippedAgent Builder
The engine. Define inputs → logic → output. Powers the AI Project Manager already.
NowQuoting agents
Spin up agents in the quoting space on the engine we already shipped — low marginal cost.
Maturing · the north starEstimating agent
- Assisted — inputs + price-lists → priced estimate
- Drawing-assisted — takeoff you confirm
- Agentic — full takeoff
Held as a direction we walk toward — the price-list work quietly
makes the first phase almost free.
How we steer it
Fund it by domain,
report it monthly.
Logistics
Compounds fastest
The monthly rhythm
A one-page allocation
- Start of month — agree the split across domains. That's the priority call, in the owner's language.
- End of month — the same sheet flips to delivered, grouped by domain.
- Delivery stays fluid; the owner gets a stable scorecard every single month.
The first month · a proposal
A logistics-first start.
Logistics & procurement~70%
Foundations · role / scope layer~10%
The role/scope groundwork is small now — and the keystone next month's
per-role views stand on.
The blocks
01 PM logistics loop + material schedule on the Gantt
02 Supplier price lists → semi-automatic call-offs
03 Variations from the original budget
04 PO delivery time slots + version history
05 Role / scope layer — groundwork
Each month: pick the blocks, ship the value,
read the results — together.