Contracts
Business-Gym has a working contracts surface. You can draft a contract, generate one from a sent quote, add line items, move it through a status lifecycle, and stage it for signature behind a human approval. What it cannot do yet is deliver the document: the e-signature connector is dark, so nothing reaches the counterparty from inside the product.
Nothing on this surface acts on its own. Contract work is propose-only, like the rest of the platform — see autonomy and the hard floor.
Where do contracts live?
Section titled “Where do contracts live?”They live under Legal in the sidebar, which opens the contracts list. The nav item says Legal and the page heading says Legal, because contracts share the surface with two neighbours: Contracts, Compliance and Renewals are three tabs on the same page.
The Contracts tab is a searchable table — number, type, counterparty, value, status, end date — with filters for type and status and a sort by most-recently-updated or by number. Clicking a row opens the contract builder.
How does a contract get created?
Section titled “How does a contract get created?”Two ways, both started by a person. You either press New contract on the Contracts tab and fill in the form, or you generate one from a quote that has already been sent.
The New contract form captures title, type (MSA, SOW, NDA, DPA, order form, amendment, other),
counterparty kind, customer, your legal entity, owner Head, value, currency, start and end dates, notice
days and renewal term. Each contract gets a per-tenant number in the form C-2026-0001.
From a sent quote, the quote builder shows a Generate contract button. It copies the customer, owner, value, currency and every line item into a new draft contract and links it back to the quote. It is idempotent — pressing it twice returns the same contract rather than making a second one.
What can you edit, and when?
Section titled “What can you edit, and when?”Header fields and line items are editable only while the contract is Draft or In review. Once it moves past those states the builder locks the fields, and the API rejects a header edit with a plain error rather than silently dropping it.
The status ladder is Draft → In review → Out for signature → Signed → Active → Expired, with Terminated reachable from most states. Moves that do not make sense are refused: you cannot jump a draft straight to signed.
Line items take an offering from your catalogue or a custom line, each with a quantity and unit price, and the builder shows a lines subtotal.
Creating and editing are owner and admin only. Other members can read the list, open the builder and read the renewals sweep, but the write controls are not shown to them.
What happens when you send a contract for signature?
Section titled “What happens when you send a contract for signature?”An approval gets staged, and nothing is sent. The Send for signature button becomes available only once a contract is In review — a draft has to be moved there first — and pressing it creates a pending item in the approvals queue with the contract summary attached.
The contract stays In review while that approval waits, and the builder shows a banner saying the contract is awaiting signature approval. Pressing the button twice does not stage two approvals.
When a person approves it in the approvals queue, the contract moves to Out for signature and the decision is written to the audit log. That transition is the whole effect of the approval today.
Can Business-Gym actually get a contract signed today?
Section titled “Can Business-Gym actually get a contract signed today?”No. DocuSign is not connected. It appears in the integrations catalogue marked “Coming soon” and is inert — there is no envelope, no email to the counterparty, and no signature reference recorded.
The product says so rather than pretending otherwise. The signature panel on a contract reads that the e-signature connector is not configured yet, and the awaiting-approval banner repeats it: approving only records the staged send.
This is the same rule as everywhere else in the platform — external sends are human-approved, and a step that cannot really happen reports itself as not connected instead of faking success. The inbound → approve → execute loop explains why.
Where do NDAs, DPAs and renewals show up?
Section titled “Where do NDAs, DPAs and renewals show up?”On the other two tabs of the same page. Compliance is a register of legal documents — kind, title, customer, effective date, expiry, retain-until date and status — that you add, edit and remove by hand. It is a record of what exists, not a generator.
Renewals is a read-only sweep of your live contracts. It reads each signed or active contract’s end date and notice period and buckets them into overdue, due now and upcoming over a 180-day horizon, most urgent first, with a roll-up at the top. It only tells you; it never sends a notice or renews anything.
What is not available yet?
Section titled “What is not available yet?”E-signature delivery, automatic drafting, and any form of clause intelligence in the contract builder. Specifically, none of the following exist on this surface today:
- E-signature sending — DocuSign is dark. Approving a send transitions the status and nothing leaves.
- Automatic value totals — the contract value is typed, not computed from the lines.
- Templates or a clause library in the builder — there is no template picker and no clause bank.
- Redlining or version comparison — the builder edits fields and lines, not document text.
- Automatic renewal actions — the Renewals tab reports; it does not draft or send a notice.
- A head drafting a contract from an inbound email on its own — every contract starts with a person.
One related piece does exist elsewhere: the workflow library ships a Contract intake and risk triage template that classifies a received contract’s risk, drafts advisory redlines and gates them behind counsel approval before filing. It is triggered by an API call, not wired to your inbox by default, and it never sends anything to the counterparty. Treat it as a template you would have to set up, not as behaviour you already have.
Every contract action — created, generated from a quote, staged for signature, sent for signature — is written to the audit log with who did it.