Skip to content
growthcontrolBook a consultation
Home/Platform/Atticus

Atticus by Growth ControlCRM contract
automation.

From agreed CRM terms to a reviewed contract and electronic signatures. Atticus is designed to prepare contracts from approved templates, track buyer and owner signatures, and connect the signed agreement to the next step in your sales process.

Planned · first rollout scoped for Stretch Tent

Atticus prepares a Stretch Tent agreement for review and tracks buyer and owner signatures. Planned workflow.

Prepare contracts
from CRM deal terms.

The price is agreed. The document should reflect it.

Copying a quote into a contract creates another place to check the amount, scope, dates and payment terms. A revised attachment can leave your team unsure which version the customer received.

Atticus is designed to prepare the agreement from the terms recorded in your CRM and an approved template. Each version stays linked to those terms, its attachments and the people who need to sign.

From CRM terms
to two signatures.

The planned process keeps document preparation, approval, signatures and billing distinct.

1. Check the agreed terms
Read the deal type, buyer, scope, price, dates and payment terms from the CRM. Missing or conflicting details come back as a specific list to resolve.
2. Prepare the contract
Fill the approved template and include the required attachments. Keep a version linked to the deal terms used to prepare it.
3. Review before sending
You see the PDF, attachments, recipients and message. Approval covers that exact version. A material change requires a new review.
4. Track both signatures
For the first Stretch Tent rollout, the buyer signs in Documenso, then the owner signs separately. The buyer’s signature alone does not complete the process.
5. Move the deal forward
After both signatures are confirmed, save the signed file and signing record. The configured workflow can mark the matching deal Won and request a deposit invoice from Pacioli for separate approval.

What connects CRM
and e-signatures?

The planned Stretch Tent setup uses agreed deal terms from Twenty CRM and electronic signing in Documenso. The CRM remains the source of the buyer, order scope, price, dates, deposit and balance terms. Atticus checks those details before preparing the document.

After your review, the approved version goes to the buyer and then to the owner for signature. The signed agreement stays linked to the deal; a billing request goes to Pacioli under its own invoice approval rules.

Documenso is installed at Stretch Tent. The Atticus integration is planned; other CRM and signing-provider connections are scoped before implementation. See how CRM workflow implementation works.

The buyer signed.
What happens next?

Illustrative Stretch Tent sale · fictional customer · no document is sent

A Stretch Tent customer agrees to buy a custom tent. Its order details and payment terms are recorded in the CRM. Atticus prepares the contract, and the owner reviews the exact PDF before approving delivery.

Buyer signed → waiting for the owner. The deal stays open while the owner reviews and signs in Documenso.

Both signed → agreement complete. Once the current agreement is confirmed, the configured process marks the deal Won and asks Pacioli to prepare the agreed deposit invoice. The owner reviews the invoice before it is issued.

A signed agreement, a Won deal, an issued invoice and a received payment remain separate records.

Review each version.
Approve before sending.

Atticus uses approved templates and agreed commercial terms. It does not choose your price, accept legal changes or sign on your behalf.

If a buyer asks for a change, your sales process agrees the update and records it in the CRM first. A replacement contract gets a new version and approval; an active earlier signature request must be withdrawn before its replacement is sent.

A completed agreement keeps its original signed terms. Changes after signing need a separately defined amendment process.

First rollout:
Stretch Tent custom sales.

Planned for custom tent sales at Stretch Tent. The first scope combines CRM deal terms, approved contract templates, Documenso signing, owner review and a deposit-invoice handoff.

Documenso is installed for Stretch Tent. The Atticus integration and end-to-end workflow are planned and require implementation and validation before use. Rentals remain in the billing process without an Atticus contract.

Other contract types are scoped around your templates, required fields, signers and completion rules. Automatic signing reminders, new legal drafting and obligation tracking are outside the first rollout.

Connect contracts,
sales and billing.

Each part has a clear job in the configured workflow.

Figaro · commercial terms
Coordinates proposed changes with the owner so the CRM can hold the agreed terms before contract preparation.
Atticus · agreements
Prepares the approved document, tracks versions and confirms who has signed.
Pacioli · billing
Receives the signed agreement’s payment terms and prepares the invoice under its own approval rules.
Growth Control · shared process
Keeps permissions, approvals and action history connected to the customer record.

CRM contract automation:
questions answered.

Is Atticus available today?

The first Stretch Tent rollout is specified and planned. Documenso is installed; the Atticus integration still needs implementation and end-to-end validation. Discuss your workflow to scope a deployment.

Does Atticus write legal terms?

The first version fills approved templates with agreed deal terms. New legal language and review of proposed legal changes stay with your designated reviewer.

Can it send or sign without me?

The first rollout requires the owner’s approval before sending. The owner signs separately in Documenso. Approving delivery does not authorize Atticus to sign for you.

What if the customer changes the order?

Agree and record the new terms first, then prepare and approve a new contract version. Replacing an active signature request requires withdrawal of the earlier request. Signed agreements keep their original terms.

Does a signature automatically mean payment?

No. Both signatures can trigger the configured Won update and an invoice proposal. Invoice approval, delivery and confirmed payment have their own statuses.

Can it use our existing contracts?

We scope your approved templates, required fields, attachments, CRM mapping and signing rules before enabling the workflow.

Less document handling.
A clearer path to signing.

Tell us how you agree terms, prepare contracts and collect signatures. We’ll scope the steps, templates and approval rules around your business.

Discuss your contract workflow
Planned product · implementation and supported integrations scoped per setup.