One gated intake path, from first conversation to property setup.

Case study · Client onboarding

One intake path, from first conversation to property setup.

Taking on a new managed property used to move through forms, emails, commercial terms, contract drafts, folders and property records as separate tasks. Every document had a purpose. Somebody still had to know the order, notice what was missing, copy facts into the next document, and remember which version had been approved.

An owner-only private pilot connects intake, terms and review. Live email, contract generation, signature, canonical file writes, property activation and property-directory writes remain disabled until their approval gates are complete.

Discuss work like this The rest of the systems practice

The problem

It was never too many forms.

Each document in the original collection was defensible on its own. The difficulty was that nothing connected them. The same information was asked for more than once in different words. Commercial terms lived in one place and contract language in another, and reconciling them was a person’s job. Answers arrived incomplete and had to be chased. Approved facts then had to be translated by hand into the setup of an actual property.

What was missing was one controlled workflow joining the forms, the people, the decisions, the contract boundary, the file lifecycle, and eventually the physical property record. The property’s own record begins later, in the directory that is the source of truth for its physical components, so everything before that needed a governed path into it rather than a handoff by memory.

What I designed and built

One path, with a gate at every point where judgement is required.

The pilot’s designed workflow: candidate to setup

  1. An employee opens a candidate property record and completes a short fit check.
  2. Management approves or rejects the fit before client work expands.
  3. The employee sees the standard commercial terms on one page and either selects an approved option or records a documented exception.
  4. Management approves that exact version of the terms. A hash of the snapshot means a later edit cannot inherit an earlier approval.
  5. The system prepares a branded invitation for the client.
  6. The client completes six plain-language sections: owner and legal entity, property and building, compliance and insurance, listing and guest experience, vendors and maintenance, technology and access.
  7. An internal reviewer returns only the sections that need correction, and the resolution is recorded.
  8. The client receives one consolidated final review and confirms the facts and the approved terms. That confirmation is explicitly not a signature.
  9. A contract packet manifest is bound to its sources and stops at a release hold until the owner, counsel, provider and send gates are all satisfied.
  10. After execution, a deterministic setup plan carries stable owner, property and folder identities forward, and stages only eligible physical facts for verification.

The value is in the connections, not the steps. One approved terms snapshot is the same version used at client review and again at contract release. One client answer has a defined destination instead of being recopied wherever somebody remembers it belongs. One property identity survives the move from candidate record to active property and later verification.

Why this is not a form

It joins disciplines that usually run as separate workstreams.

Process and product

A document collection becomes an ordered state machine with explicit entry, approval, correction, release and activation gates. Each role sees only the work appropriate to it, in plain language, with save, resume, correction and final-review paths.

Contract and legal operations

Approved business terms connect to the contract release packet, counsel and owner gates are preserved, and a client’s confirmation is prevented from being treated as a legal signature.

Identity and authority

Staff reuse the existing Workspace authentication boundary, client sessions are separate, access is denied by default, and neither self-approval nor approval by an unauthorised identity is possible.

Data and records

Stable identifiers, versioned policy, immutable snapshots, integrity hashes, a relational state store, and provider-neutral boundaries for email, signature, filing and the property directory. Owner-reported facts stay separated from field-verified ones.

What it is designed to recover

Four to seven hours of internal staff time per new property.

This is a workflow estimate for a private pilot, not a measured production result. It models internal staff handling time across creating the candidate record, assembling and approving terms, distributing and consolidating intake, describing corrections, reconciling facts into the contract handoff, and staging setup identities. It excludes client completion time, legal review, management decision delays, signature waiting, physical inspection and unusual contract exceptions. It will be replaced with observed staff handling time once the controlled pilot produces data.

What it is not: it is not labour eliminated and it is not headcount. It is capacity returned to client review, judgement, communication and getting a property actually ready.

Contact

Bring the process nobody can hand to somebody else.

info [at] thinksynergy.biz