One engine. Many roles. Content and configuration, not code.
Each worker is a definition, plus a knowledge scope, plus an asset scope, plus a set of adapters and grants. That is what allows a role as different as a collections specialist to run on the same runtime as an enterprise seller. The B2B inside sales representative is the first release, and it was chosen deliberately because it is the hardest case the platform is likely to face.
The strongest evidence that the engine boundary is drawn correctly is that we have already pointed it at a second industry. An enterprise sales worker in Singapore and a property operations worker in Indonesia share the tool schema, the outcome contract and the conversation architecture. What differs is content: vocabulary, briefings, escalation boundaries, disclosure phrasing per language, and the ethical posture for vulnerable contacts.
A domain with genuinely vulnerable counterparties required no engine change at all, only a different template, a different guardrail set and a different ladder. If that is the whole difference, the boundary is in the right place.
Each worker below is the same object: a definition the runtime executes. The difference between them is which ladder they pursue, which knowledge they draw on, and which systems they write back into.
Navigates organisations, follows referral chains, detects initiatives before they become formal procurements, qualifies progressively against your methodology, and books meetings with the people who actually decide.
Explore the ISRarrow_forwardOwners listing or renting, buyers, agents migrating portfolios, developers marketing inventory, and institutions handling collateral. Proof that the engine carries a completely different industry.
How portability worksarrow_forwardDeal guidance, call preparation, post call debrief, longitudinal skill analysis, and objection rehearsal against a simulated contact. Grounded in governed methodology rather than generic advice.
How coaching worksarrow_forwardTracks contract expirations well ahead of the date, monitors utilisation for both churn risk and expansion signal, notifies stakeholders when releases ship, and steps in when support escalates.
Systems it connects toarrow_forwardTakes an asset request raised by another worker, drafts the one pager or localised deck from governed knowledge, and submits it for approval before publication. The point at which a hub becomes a fleet.
The request boardarrow_forwardReview meetings, adviser follow up and information packs, over licensed wealth management domain content and a core banking system of record.
Domain contentarrow_forwardArrangement agreed, hardship review, specialist referral. A ladder where the ethical guardrails matter more than the conversion, and where the platform's consent machinery earns its place.
Guardrailsarrow_forwardTerms confirmed, clarification meetings, escalation, against an ERP and a contract repository rather than a CRM.
Adapter modelarrow_forwardDrift detected, cluster triaged, revision proposed. A supervisory worker whose authority is a strict, enumerated subset, and which may never approve its own proposals.
Supervision modelarrow_forward| Worker | Primary ladder | Systems of record | Domain content |
|---|---|---|---|
| Inside Sales | Executive meeting, then stakeholder meeting, then account team follow up | CRM, calendar, workspace | Sales methodology, product and competitive knowledge |
| Property Operations | Consultation, then stakeholder meeting, then specialist follow up | Listing platform, enquiry and offer workflow | Market, legal and transaction knowledge |
| Domain Coach | Skill gap identified, then rehearsal completed, then measurable improvement | The Hub's own evidence base, plus CRM | Methodology library, objection handling, conversation examples |
| Customer Success | Renewal secured, then conversation scheduled, then escalation routed | CRM, entitlement and usage systems, service desk | Product, entitlement and support knowledge |
| Marketing | Asset published, then draft in review, then brief clarified | Asset library, brand system | Brand, positioning and content knowledge |
| Relationship Assistant | Review meeting, then adviser follow up, then information pack | Core banking, portfolio and CRM systems | Licensed wealth management content |
| Collections & Workout | Arrangement agreed, then hardship review, then specialist referral | Servicing and collections platform | Regulatory and hardship handling content |
| Fleet Manager | Drift detected, then cluster triaged, then revision proposed | The Hub itself | Scoring rubrics and calibration policy |
The platform adapts to your existing infrastructure rather than requiring you to change your workflows. Knowledge and intelligence population run in parallel over a longer period, and deepen continuously after launch.
Voice first, real time, multilingual, regulated, and commercially measurable. If a runtime can carry an enterprise inside sales representative, it can carry almost anything.