Service Proposals

What you can do

• Multi-option proposals

  Send up to five priced options on a single proposal. Each option carries its own scope, professional fee, payment schedule, indicative timeline, government fees, and service components. Mark one as the recommended option; the prospect can accept any of them.

• AI Populate from intake notes + ID documents

  Upload consultation notes, IRCC letters, and passports. Claude reads them directly (no text-extraction step), recommends a Service Agreement template that matches the matter, proposes a fee based on what the operator's prompt or documents stated, identifies family members with their roles and accompanying-status, and surfaces field-by-field proposals you can accept or discard per row.

• Encrypted client portal

  Each recipient gets a per-recipient secure link with an email-gate identity check. The portal shows every option side-by-side with totals, included people, and gov-fee disclosure. Prospects can accept, counter-offer, or decline (with optional reason) from the same portal.

• Structured numeric counter-offers

  Counter-offers are not free-form emails. The prospect enters a numeric counter-fee + structured scope additions / removals + an optional note. The tenant sees the delta highlighted in the dashboard counter-review surface, accepts (spawning a new option) or rejects with one click, and the audit ledger records every step.

• One-click conversion to Service Agreement

  When a prospect accepts an option, the tenant clicks Convert. The accepted option's client identity, family members, matter framing, scope, professional fee, payment schedule, government fees, indicative timeline, and the applied template version flow into a pre-filled SA draft. You review and finalize through the existing Service Agreement Builder.

• SA-grade Government Fees catalogue

  Pick from 300+ IRCC, CBSA, IRB, and provincial / territorial fees curated by Investatech using the same breadcrumb-navigated picker the Service Agreement Builder ships with. Per-unit amount hints, override-with-reason flow for tenant-specific cases, and a separate Custom / provincial path for Quebec program fees or one-off disbursements.

• Automated reminders + 30-day expiry

  If the prospect doesn't decide within day 2, day 5, and day 9, the platform sends reminder emails with token rotation (the previous link stops working). After 30 days without a decision the proposal auto-expires. A per-recipient unsubscribe link is honoured.

• Per-recipient decision authority

  Each recipient is tagged as Decides, Advises, or Informed. The validator requires at least one Decides recipient before send. The portal surface respects the role: Advises and Informed see the proposal but cannot accept or counter.

• Send-time validator + checklist

  The right-rail Send checklist enforces blockers in real time: every option needs a matter, at least one included person, a payment schedule that sums to the professional fee, priced service components that reconcile to the professional fee, a recipient with Decides authority, and the bilingual fallback language when the proposal locale is non-official. Warnings (e.g. no government fees itemized) nudge the operator without gating send.

• Encrypted at rest under your tenant key

  Every proposal — client identity, family roster, options, recipients, counter-offers, uploaded context documents — is encrypted at rest under your tenant's data encryption key. Audit events are append-only with an UPDATE-immutable trigger so the legal-defensibility record cannot be tampered with after the fact.

• Preview HTML matches what the prospect sees

  Click Preview to see the exact HTML the recipient renders in their portal — same identity card, same matter framing, same section order (Matter → Included → Scope → Service components → Payment schedule → Government fees → Indicative timeline → Notes), same tax line, same totals. No guessing.

• Audit ledger from first keystroke

  Every state change — proposal created, option added or removed, recipients updated, proposal sent, recipient invited, portal viewed, counter received, counter accepted or rejected, decision recorded, converted to SA — lands in an append-only ledger with the actor, timestamp, recipient context, and any metadata. The same chokepoint your Service Agreements use.