Setup

What it needs
from you.

The pack is being prepared for a small invited group. This is what it asks for, what happens before it is installed, and what it will not do.

Your profile

The part only you can write

The hard part is not the assistant. It is writing down how your business actually prices and runs work — and most of it has never been written down anywhere.

How you price

The method, the rate basis, what sits inside a rate and what sits outside it. The single most valuable thing in the file.

What you do not bid

So it stops rather than helps.

Your terms and claim cycle

Retention, release, defects period, payment terms, reference dates, who certifies, and what short payment usually looks like.

How your jobs are structured

Sections, tasks, cost codes, and the attribution decision behind them.

Your rates, dated

Nothing here is used until it is filled in and carries a date.

Your risk thresholds

A four per cent civil job and a thirty-five per cent fitout cannot share a setting.

An unfilled section is not permission to guess — it is the reason to stop. The pack does not build on a profile that is still blank where it matters.

Before installation

Four things to settle first

A named commercial reviewer

One person who owns what the assistant may do, and the only one who widens it.

An account that can carry it

Your own assistant account, checked for what the pack depends on. If something essential is not available, the workflow is narrowed rather than fudged.

Agreed data

Exactly which exports it may read, and which it may not. Read-only.

An acceptance run

Worked examples with known answers, run on your installation, before it sees a live job.

The boundary

Everything starts as a draft

One named person at your business owns the table and is the only one who moves anything up it — after the checks have passed on real work, repeatedly. Reviewed monthly.

Draft

It produces it. A person reads it, edits it, and sends or applies it. Everything starts here.

Propose

It recommends a specific action. A person approves it unchanged, or rejects it.

Act

A possible later permission for a narrowly defined, tested non-financial task. It is outside the initial pilot; no task starts here.

Some things never move, whatever the level: anything that commits money, anything sent under someone’s name without them reading it, accepting terms, changing an issued claim, and deleting records. Placing an order is a person’s job. The planned pack prepares drafts and follow-up questions for a person to review and send.

Either assistant

The same pack, whichever one you use

Written once

The same business definitions are being prepared for Claude and ChatGPT. Each supported setup must pass its own acceptance tests; wording and behaviour may differ.

It runs in your account

The proposed pilot uses approved exports in your own assistant account, subject to its plan and data settings. Contractable will not combine customer profiles into a shared knowledge pack.

Support uses what you choose to share

The proposed workflow does not give Contractable access to your assistant account. Support uses the records or examples you explicitly choose to share.

Talk it through

Start with the job, not the tool

If you want to work out whether your business is in a position to get value from this, the first conversation is about how you run jobs now.

Or email hello@contractable.co.