Skip to content

Engagements and payment ​

An engagement starts when the client chooses an option and pays, or when the advisor records a commitment made outside DutyGraph. Until then the company stays a prospect, and Discovery and the Work Map stay closed.

The options ​

The advisor prepares the options in the account drawer: Activation › Prepare proposal. Each option combines a scope and a plan.

One-time auditLiving DutyGraph
Named departmentsAvailableAvailable
Whole companyAvailableAvailable
  • The composer is prefilled from the sponsor's review: the departments they named and the sponsor the advisor accepted as the recipient.
  • Prices come from the firm's price book. This page does not list prices.
  • A whole-company price needs a headcount band from a confirmed source. Without one, the option reads "Price confirmed after your team list" and can go only to a statement of work (SOW).
  • Living DutyGraph starts after the initial audit and bills on a recurring cadence (monthly by default) with a minimum term. See Living DutyGraph.

The advisor selects Send by email or Create link to copy. Sending new options withdraws the earlier open ones.

What the client does ​

The client opens a private, phone-first proposal page with three parts:

  1. What should DutyGraph cover?
  2. Choose your plan
  3. Summary, with an estimated duration (labelled an estimate), the refund and cancellation policy, and a required acceptance checkbox.

The client then picks one of the payment paths the advisor allowed:

PathWhat happens
Pay by cardStripe-hosted Checkout. DutyGraph shows no card fields and stores no card numbers. A one-time audit is a single payment. Living DutyGraph is a subscription.
Send me an invoiceDutyGraph creates a Stripe invoice, with a field for a purchase order number, and Stripe sends it.
We need a signed SOW or purchase orderThe advisor handles the document and records the commitment afterwards.

The acceptor's email is fixed to the contact the link was sent to. The client submits only which option they chose. The totals come from the frozen offer, not from the browser.

WARNING

The refund and cancellation text is a draft pending legal review.

How the engagement activates ​

Card or invoice ​

Stripe sends DutyGraph a webhook event when a Checkout payment or an invoice is paid. DutyGraph accepts the event only when:

  • its Stripe-Signature header matches an HMAC computed with the webhook secret, within a 5-minute window;
  • the event type is on an allowlist and its mode (live or test) matches the key;
  • the Stripe object matches the provider id stored on the offer, and the offer is still live;
  • the amount and currency match the frozen offer.

When every check passes, DutyGraph activates the engagement as the system actor, with the Stripe reference. Nobody types anything. Each Stripe event is processed once. A mismatch never activates: DutyGraph flags it and emails the advisor.

Later Stripe events move the engagement too: a renewal payment, a failed payment (past due), a cancelled subscription, a refund or a dispute.

A commitment made outside DutyGraph ​

For an accepted proposal or SOW, an enterprise contract, a design-partner authorization or an advisor-paid engagement, the advisor records the commitment on the Activation tab.

  • Every method needs a note. Some need a reference too.
  • When the workspace has two or more advisors, these methods need a second advisor to approve. The approver can never be the requester.
  • A firm can turn methods off for itself. It cannot remove the platform's second-approver rule.

Every activation applies the client's accepted option. It writes the purchased scope onto the company, such as "Whole company" or the named departments.

Confirmation ​

After activation, the client gets one DutyGraph email with the scope, plan, reference, dated next steps and the advisor's contact. The advisor gets one notice. A replayed event sends nothing.

Share a company ​

A company can be shared with people outside the owner's workspace, such as the client's team or another advisor. Open Settings › Members & roles.

RoleCan do
AdminEverything, including managing members and exports
AssistantDay-to-day work: edit the company, Work Map and records, run and review research, billing, connections and interviews. Not member management or exports.
Read-onlyView the company, Work Map, research and records
  • The workspace owner is an implicit Admin. A company always keeps at least one Admin.
  • An Admin invites by name, email and role, with Copy private link or Send email. Links expire after 7 days. DutyGraph stores only a hash of each link.
  • The invitee proves they own the email address with a one-time code before they can accept.
  • The server checks the member's current role on every request. Removing someone blocks their next request.
  • Shared members never see firm-wide data. They do not see the Inbox or Companies.

INFO

Status. Built: options by scope and plan, the proposal page, Stripe Checkout and Stripe invoices, the webhook checks and activation, commitments recorded outside DutyGraph with second-advisor approval, confirmation emails, and company sharing with Admin, Assistant and Read-only roles. Simulated: a local payment simulator stands in for Stripe in development; it is never used when hosted. Card and invoice payment are off until the server has Stripe keys. Planned: Stripe Connect onboarding, a refund button and customer portal, adding a department to an active engagement, Stripe Tax, a generated SOW document, and a firm role model for price-book edits.

Source: gitbook/product/advisors/engagements-and-payment.md in the DutyGraph repository.

DutyGraph. Pages label each feature Built, In review or Planned.