Before you start
- An active pipeline
- A test person and project
Build reusable pieces first
Open Library and create the smallest reusable pieces:
- a lead form;
- a detailed questionnaire;
- one or more booking pages;
- a service or package page;
- an agreement template;
- an invoice/payment pattern; and
- message and automation templates.
Each piece remains tenant-owned and editable. A composed journey references selected versions; it does not erase the standalone builder or force every project through the same path.
Capture only useful information
Lead forms should ask only what is needed to route and answer an inquiry. Save detailed questions for an assigned questionnaire after the person understands why the information matters.
Use sections, plain guidance, and the correct answer type. Submit malformed and incomplete tests. When a questionnaire is assigned, Cygnetree freezes the question set so later template edits do not change what the client was asked.
Make scheduling complete the appointment
Set availability, duration, notice, buffers, time zone, reminders, and host. Choose one meeting location:
- in person or a written location;
- a reusable provider-neutral link;
- Google Meet from a tenant-authorized profile; or
- Microsoft Teams from a tenant-authorized profile.
The booking is still valid if a provider meeting call fails. The missing link remains visible and retryable; Cygnetree does not silently switch providers or send a different host identity.
Freeze agreements and money
Review the agreement body, signer order, assigned fields, cancellation language, and delivery before sending. Each signer gets an identity-bound link only when it is their turn. Completed versions and evidence remain immutable.
Use invoice items and installments with exact minor-unit amounts and currency. Test offline/manual payments as well as Stripe test Checkout. A payment failure never reduces the balance, and refunds or disputes remain visible as ledger events.
Compose a client journey
A service page can connect service selection, questionnaire, contract, payment, scheduling, and welcome copy. Choose sequential or parallel progress, explain what unlocks each step, and preview the exact frozen definition before launch.
Do not send a journey only because a package was selected. Review the project, person, amounts, dates, templates, recipients, and selected providers first.
Test from the client's side
Use a test person and project:
- Open the public entry point on a phone-size browser.
- Complete the form and verify project creation and source attribution.
- Choose a service, answer the questionnaire, sign, record a test payment, and book.
- Return through the client portal and verify the next action.
- Force an expired link, provider failure, duplicate submit, and interrupted connection.
- Confirm the workspace sees useful state without exposing internal notes or false read claims.