Getting Started: workspace setup and first value
Set up QuoterAgent so your team can move from zero to first proposal — and first payment — with clarity.
High-level orientation page that explains structure and decision boundaries.
In this guide
Ownership and review discipline
Change signals to watch
- workspace onboarding UI changes
- organization profile schema updates
- new setup-required fields
- template editor or defaults changes
- template category updates
- new template lifecycle behavior
- brand configuration UI changes
- proposal rendering changes
- logo or typography behavior updates
- plan architecture updates
- workspace permissions changes
- billing and subscription policy updates
Operator guidance
What this means in QuoterAgent
Use this guide as the operating reference for Getting Started: workspace setup and first value. It explains what this surface controls, what good execution looks like, and which teams should keep it trustworthy over time.
- QuoterAgent takes a client brief, generates a structured proposal with scope, pricing, and timeline, and supports the full commercial lifecycle through to payment confirmation. This guide covers the five things you need to set up before any of that works reliably.
- Each setup step has a downstream consequence. Missing the Stripe connection means the execution panel will create a payment session but the client will never see a checkout link. Missing the Brand Kit means proposals render with placeholder styling. Skipping a language setting means the AI may generate scope content in English even if your client expects French or German.
- Primary owners currently covering this area: Product, Growth, Support.
What to do
Treat this as a working checklist, not background reading. Use it before you change settings, publish external material, or hand work to another operator.
- Work through this guide once when you first sign up. Return to it if you change your Stripe account, rebrand, or add a new team member who needs to understand the setup dependencies.
- Once setup is complete, move through the first-value path in order: create a proposal from an intake brief, review and edit the AI-generated scope, send to your client, and when they sign, open the execution panel to initiate the kickoff payment.
- Go to Settings → Integrations and connect your Stripe account before doing anything else.
- Open Brand Kit and upload your logo and set your brand colours.
Where it shows up in the workflow
This guide matters most when work moves between setup, authoring, buyer delivery, and post-sign execution. Use the linked guides to follow the full path instead of solving one surface in isolation.
- Setup feeds every downstream workflow. The workspace profile populates proposal headers and PDF metadata. The Stripe connection is consumed by the execution panel when you initiate a payment after a proposal is signed. Brand Kit governs how templates and live proposals render. Language settings are read by the AI at scope generation time.
- Review the related guide "Brand Kit: buyer trust signals and proposal identity" when this step depends on another surface.
- Review the related guide "Templates: reusable proposal architecture and defaults" when this step depends on another surface.
- Use "Brand Kit: buyer trust signals and proposal identity" as the next guided step after this page.
Common failure modes and risks
Most quality problems here come from drift: outdated setup, weak commercial boundaries, or teams skipping the review moment before customer-visible delivery. Use these signals to catch issues before they reach the buyer.
- workspace onboarding UI changes
- organization profile schema updates
- new setup-required fields
- Stripe setup is a hard dependency for the kickoff payment and final payment flows.
- Brand Kit affects every PDF sent to a client — it cannot be applied retroactively to sent proposals.
What this is
QuoterAgent takes a client brief, generates a structured proposal with scope, pricing, and timeline, and supports the full commercial lifecycle through to payment confirmation. This guide covers the five things you need to set up before any of that works reliably.
- Workspace profile: your company name, logo, and contact details — these appear on every proposal PDF.
- Brand Kit: your colours and typography so proposals look like they came from you, not a template.
- Stripe connection: required before you can collect kickoff or final payments through the execution panel.
- Proposal language: set English, French, or German so the AI generates scope content in the right language.
- Your first template: a reusable starting point so you are not building from scratch on every engagement.
When to use
Work through this guide once when you first sign up. Return to it if you change your Stripe account, rebrand, or add a new team member who needs to understand the setup dependencies.
- Before sending your first proposal to a client.
- Before attempting to collect payment — Stripe must be connected first.
- When onboarding a new operator who will manage proposals independently.
Why it matters
Each setup step has a downstream consequence. Missing the Stripe connection means the execution panel will create a payment session but the client will never see a checkout link. Missing the Brand Kit means proposals render with placeholder styling. Skipping a language setting means the AI may generate scope content in English even if your client expects French or German.
- Stripe setup is a hard dependency for the kickoff payment and final payment flows.
- Brand Kit affects every PDF sent to a client — it cannot be applied retroactively to sent proposals.
- Proposal language drives the AI scope generation, not just the UI language.
How it connects
Setup feeds every downstream workflow. The workspace profile populates proposal headers and PDF metadata. The Stripe connection is consumed by the execution panel when you initiate a payment after a proposal is signed. Brand Kit governs how templates and live proposals render. Language settings are read by the AI at scope generation time.
- Stripe → execution panel → kickoff payment → activation → final payment → closeout.
- Brand Kit → every proposal PDF and buyer-facing send page.
- Language → AI scope generation → proposal section content.
Next steps
Once setup is complete, move through the first-value path in order: create a proposal from an intake brief, review and edit the AI-generated scope, send to your client, and when they sign, open the execution panel to initiate the kickoff payment.
- Go to Settings → Integrations and connect your Stripe account before doing anything else.
- Open Brand Kit and upload your logo and set your brand colours.
- Read the Proposal Authoring guide to understand how intake, AI generation, and scope editing work together.
Related guides
Brand Kit: buyer trust signals and proposal identity
Configure Brand Kit so every proposal reflects a consistent, credible buyer-facing identity.
Open guide
Templates: reusable proposal architecture and defaults
Use templates to scale quality, speed, and consistency without lowering proposal specificity.
Open guide
Proposal Authoring: from intake to send readiness
Run a disciplined proposal workflow that aligns executive summary, scope of work, and pricing signals.
Open guide
Next guide
Brand Kit: buyer trust signals and proposal identityUse this before external sharing, after rebrands, or when proposals feel generic.