Keep the commercial and payment states separate
| State | Evidence to keep |
|---|---|
| Terms agreed | Buyer, scope, price, dates and payment schedule recorded by the sales process. |
| Document approved to send | Exact version, attachments, recipients and owner approval. |
| Agreement complete | Required buyer and owner signatures confirmed on the current version. |
| Invoice issued | Separate billing approval and provider invoice reference. |
| Payment received | Confirmation from the payment provider matched to the invoice. |
Decide when Won applies to your process. In the planned first Atticus custom-sale flow, both signatures can trigger the configured Won update. That does not make Won a universal synonym for paid revenue.
Agreed terms
Sales confirms the facts.
Document review
Approve the exact version.
Two signatures
Confirm agreement completion.
Billing review
Approve a separate invoice.
Planned custom-sale workflow. A signature is not an invoice or a payment.
How Figaro, Atticus and Pacioli divide the work
- The sales process agrees terms. Figaro can help coordinate proposed changes with the owner so the CRM contains the approved facts.
- Planned Atticus checks those facts and fills an approved contract template. Missing or conflicting terms return for resolution.
- The owner reviews the exact document before sending. Buyer and owner signatures are tracked separately in the planned Documenso connection.
- Once completion is confirmed, the configured workflow can save the signed record and request a deposit invoice from Pacioli.
- The owner separately reviews the invoice. Issuance, delivery and payment status use the connections enabled for that installation.
Atticus is planned and requires implementation and end-to-end validation. Documenso being installed does not mean this integration is live. Pacioli’s Mercury/Stripe integrations are confirmed; automated handoffs are enabled and checked per setup.
Prepare a document packet that can actually be reviewed
A useful review packet includes more than a PDF. The owner should see the CRM terms used to prepare it, the specific template/version, attachments, recipients and the proposed delivery message. That lets the reviewer check the offer against the source instead of trying to remember which discussion produced the document.
| Check | Question for the reviewer |
|---|---|
| Parties and order | Does this document concern the correct buyer and custom-sale opportunity? |
| Scope and dates | Do the included items, exclusions and timing match the agreed terms? |
| Amounts and schedule | Do total, deposit, balance and due dates agree with the CRM source? |
| Files and recipients | Are these the intended attachments and people for this exact version? |
| Approval boundary | Is the approval to send recorded separately from either person signing? |
The first planned Atticus workflow fills approved templates; it does not resolve a disagreement about legal language. An unanswered commercial question must return to the sales process, and a requested legal change needs the designated reviewer.
Worked example: a custom Stretch Tent sale
Fictional Stretch Tent custom-sale example. The amounts and conditions are invented for explanation, not an actual tent offer.
Assume the approved order total is $2,400, with a 40% deposit and $1,440 balance. The deposit calculation is $960. Before document preparation, the team must also record the agreed due dates and order scope. A percentage alone is not a complete payment schedule.
Planned Atticus prepares the reviewed template using those facts. The owner checks the document and approves its delivery; this is not the owner’s signature. The buyer then signs the current version in the planned Documenso flow. Until the owner separately signs, the required two-signature completion condition has not been met.
Once both signatures are confirmed, the configured completion rule can save the signed agreement, record the relevant commercial outcome and request the $960 deposit invoice proposal. Pacioli’s separate invoice approval still applies. A provider invoice reference records issuance; a confirmed payment event establishes payment. The $1,440 balance remains a separate future billing obligation under the agreed business rules.
Each transition should be explainable from its own evidence. Do not infer payment from a signature or invent a due date because the previous example used one. These steps describe a planned integration requiring validation, not a shipped end-to-end Atticus result.
Handle a changed quote before replacing the contract
- Resolve the commercial change and record the new terms before preparing a replacement.
- Approve the new version; do not reuse an approval for a different amount or attachment.
- Withdraw an active earlier signature request before sending its replacement through the defined process.
- Keep completed agreements intact. An amendment after signing needs a separately defined process.
Atticus does not create new legal language, accept legal changes or sign for the owner. Automatic signing reminders and obligation tracking are outside the first rollout.
Review changes and ambiguous completion events
Before signing is complete, a changed event date, amount or attachment may require a replacement version. Identify the active request and withdraw it through the defined process before its replacement is sent. The new packet needs a fresh review. Keeping two apparently current requests invites the customer to sign terms the owner no longer intends to offer.
- Only one required signature confirmed: preserve the incomplete state and show what is still needed.
- A completion event is delivered twice: verify the same agreement reference and avoid a duplicate invoice request.
- CRM terms differ from the document: stop the handoff and resolve which terms were agreed.
- An already signed order changes: keep the original signed record; use a separately defined amendment process.
Use synthetic examples for each branch during acceptance. The owner confirms the correct terms; the integration maintainer verifies references and completion handling. An agent should not choose between conflicting versions simply to keep the process moving.
Test the handoff with synthetic records
Rehearse a missing amount, one signature only, a changed scope, a duplicate completion event and a failed invoice request. Confirm who reviews each exception and which states stay unchanged. A completed signing test is not proof that the billing handoff works.
Questions and answers
Does a buyer’s signature complete the first Atticus workflow?
No. The planned Stretch Tent flow requires the buyer and owner to sign.
Does Atticus handle Stretch Tent rental agreements today?
No. The first planned scope is custom tent sales. Rentals remain outside that contract flow.
Does approval to send authorize the owner’s signature?
No. The planned workflow separates document delivery approval from the buyer and owner signatures.
Can an old signing request remain active after terms change?
The planned replacement process requires identifying and withdrawing the earlier active request before sending its replacement, with fresh review of the new version.
Sources and further reading
Put the process into practice
Growth Control implements the tools, workflow and team handoff around an agreed business result.
Explore cRM and marketing automation built around your sales process