Approach
Low-risk on purpose: assess, pilot, then operate
GEN never starts with a platform replacement or a firm-wide rollout. It starts with one workflow, measured against a baseline, accepted explicitly — then it earns the next one.
The three phases
Workflow Assessment
Interviews with the people who do the work, a map of your current systems and data, a baseline of the measures below, and a pilot plan with named acceptance criteria. You keep the assessment either way.
Implementation Pilot
One team, one list, one workflow, for an agreed duration. Deliverables: reconciled records, a named owner and next action on every record, a stale-record queue, follow-up drafts for human approval, and a weekly operating report. The pilot ends with an explicit accept-or-stop decision. See the first pilot for the shape in practice.
Managed Operations
GEN operates the framework with you: list quality, exception handling, the weekly review, and a monthly improvement pass — so the system stays true as the firm changes.
The build order, and why it matters
Parent standards first
Numbering, Knowledge Vault structure, the permission matrix, model routing, and provider standards are set once, at the parent level — versioned, with rollback. Everything else instantiates them.
Company blueprints second
Each company gets a blueprint instantiated from the parent standard — never a hand-copied fork. When the standard improves, blueprints update on a stated version instead of drifting company by company.
Hubs last — owner, then employees
The owner hub first, so the owner sees their whole company on the standard. Employee hubs follow, role-scoped to the slice each person works. Read how the pieces fit on the Framework page.
What GEN does not do in an engagement
- No replacement mandate. A working stack stays; GEN integrates with it where approved.
- No unapproved imports. Every import passes a fresh check of every workflow trigger before it runs — an import must never silently start sending. The rule exists because it has gone wrong before, in this industry, with real messages sent.
- No external sends without approval. Drafts are prepared; a human approves and sends.
- No silent access. Parent oversight follows the permission model: aggregate-only, or an explicit logged grant.
What gets measured
Baselines first, then the same measures every week: record completeness, duplicate rate, stale records, overdue next actions, and administrative time. We publish the measures a pilot will be judged on before it starts — and no target numbers before a baseline exists.
Begin with the assessment
One workflow, honestly mapped. That is the whole first step.