V1.2 client-work platform
V1.2 establishes the industry-neutral client-work baseline: guided setup, editable starters, people/relationships, pipelines/projects, automations, communication, client journeys, contracts, invoices/payments/expenses, scheduling, portable files, client and vendor portals, PWA field work, reporting, provider-neutral migration, tenant-owned integrations, permissions, support diagnostics, APIs/webhooks, controlled AI, and exact external-recipient engagement.
Migration now supports structured export, guided manual rebuild, and archive-first routes. Every area must be imported, rebuilt, archived, excluded, or left visibly unresolved before cutover can be approved.
V1.3 documentation as product
Documentation is versioned MDX with stable metadata, generated navigation, prerequisites, related guides, typo-tolerant search, link/anchor/capability validation, and content ownership. Learning paths now cover workspace foundations, client-work builders, automation recipes, tenant integrations, migration, industry adaptation, mobile work, security, exports, and API/webhooks.
V1.4 website preview
The website integration contract begins with authoritative Cygnetree forms, booking pages, service pages, and sign-in links. WordPress and Next.js integrations must use revocable tenant-scoped public identifiers, preserve first-party attribution, degrade to accessible links, and never place tenant or platform secrets in browser code.
The first working preview now includes a constrained multi-page brochure-site builder with private drafts and visual preview, richer safe blocks, page duplicate/reorder/archive, atomic publish snapshots, version history, restore-to-draft, pause, export, live public entry points, organization theme reuse, and attributed project/pipeline/paid-invoice summaries. It also includes a server-rendered WordPress Gutenberg block and shortcode, portable web component, typed URL/snippet helpers, server-renderable typed React link components, and first-party inquiry attribution. Structured process, gallery, team, partner, location, and payment-information sections are available with accessible image text and focal controls. Custom domains now use tenant DNS proof plus deliberate staff activation, canonical URLs, sitemap, and robots handling. Optional aggregate site and public-link counters honor browser privacy signals and store no visitor identifier.
Before dogfooding
The local code baseline is not provider or user acceptance. Staging, real tenant authorization, Stripe test operation, migration with the design partner, iPhone/PWA and emulator testing, accessibility, placeholder-brand review, documentation comprehension, budget gates, and applicable legal decisions must pass the development-to-dogfood gate.
Known limits
- Cygnetree does not host a mailbox. Managed and tenant Resend send mail; Gmail/Outlook are optional tenant-authorized mailbox integrations; SMTP is outbound only.
- A meeting-link open is recorded without claiming that a person joined or attended.
- Historical signatures, payments, and read events from another system remain archive evidence unless a supported adapter can preserve them without inventing Cygnetree activity.
- The simplified builder and link integrations remain preview work until WordPress compatibility, the provider-neutral public media plane, analytics export/alerts, accessibility, and portability gates pass.
- Templates and retention/signature language require tenant review and qualified advice for the applicable jurisdiction.