sonaris
Join waitlist

Use cases / Services

Sonaris for web agencies

From the first enquiry to the care plan: a pipeline, proposals billed by milestone, sitemaps and specs next to the sprint board, every client stakeholder in their own project room, and a go-live checklist that nobody skips.

Join the waitlist See the platform
LD
Lowtide DigitalWebsites, products and design systems · Brighton and Lisbon
  1. New business in one pipeline2 / 14CRMForms
  2. Proposals billed by milestone4 / 14CommercePayments
  3. Delivery with the client in the room10 / 14ProjectsCanvasFolioFilesChatProfiles
  4. Go-live, care plans and the flow between14 / 14FlowsChecklistsMessagesSites

An illustrative workspace. The business, people and figures are fictional.

01 · Start with CRM and Forms

New business in one pipeline

The project-planner form on the agency's site creates a contact and a deal, tagged by source. Deals move from qualified to pitch to proposal, relationship mapping shows every stakeholder at the client, and booking pages take the intro call.

  • Deals and pipelines with stage automations
  • Relationship mapping across a client's people
  • Forms that create a contact and a deal
  • Booking pages on the same contact record
CRMForms
CRM · Pipeline · New business · this quarter
Qualified
Northgate FC · app and site£140,000 · referral
Orla Health · design system£92,000 · site form
Pitch
Greywater Utilities · rebuild£180,000 · Thu pitch
Proposal
Saltmarsh Museum · collections£64,000 · sent
Greywater · 7 stakeholders mappedCRM
02 · Add Commerce and Payments

Proposals billed by milestone

Discovery sprints, design systems, builds and care plans are Commerce services with packages. A won proposal becomes a contract whose milestones match the delivery phases, invoiced into the agency's own Stripe account as each phase lands.

  • Services, packages and milestone contracts
  • Contracts drafted from the deal value
  • Invoices paid into your own connected Stripe account
CommercePayments
Commerce · Contract · Saltmarsh Museum — Collections site
MilestoneAmountStatus
Discovery sprint£12,000Paid
Design£18,000Paid
Build£28,000Invoiced
Launch£6,000Upcoming
Care plan · after launchPackage
03 · Add Projects, Canvas, Folio, Files, Chat and Profiles

Delivery with the client in the room

Each engagement is a project from the service template. The sitemap and user flows are a canvas tab, specs and decisions are Folio pages with live task tables, and design files keep their versions. Client stakeholders and freelancers join as guests, and see their project and nothing else.

  • Board, list and timeline views with saved lenses
  • Canvases with shapes, notes and connectors
  • Spec pages that embed the tasks they describe
  • Role-based permissions on every module
ProjectsCanvasFolioFilesChatProfiles
Projects · Saltmarsh Museum — Collections site · Sitemap
PageHome PageVisit TemplateCollection object PageLearn Curator · guestAdd the maker's archive link here
#saltmarsh · 6 client guests · 2 freelancersChat
04 · Connect with Flows, Checklists, Messages and Sites

Go-live, care plans and the flow between

A go-live checklist covers redirects, analytics, forms, DNS and backups, and completing it moves the project to Live. Care-plan clients write to a shared support inbox where tickets carry SLAs. The agency's own site runs on Sites, and Flows ties a won deal to a project, a contract and a client room.

  • Checklist templates that can start a flow when done
  • Tickets with SLAs for care-plan support
  • A site with portfolios, forms and custom domains
FlowsChecklistsMessagesSites
  1. Trigger · CRMDeal won
    when
  2. Action · ProjectsCreate project from “Website build”
    then
  3. Action · CommerceContract from the deal value
    then
  4. Action · ChatOpen a room and invite the client team
    then
  5. Action · ChatPost to #new-business
    then
  1. Trigger · Checklists“Go-live QA” completed
    when
  2. Action · ProjectsAdvance to the Live phase
    then
  3. Action · PaymentsIssue the launch milestone invoice
    then
  4. Action · ChatPost to #launches
    then
  1. Trigger · CRMTicket unanswered for 4 hours
    when
  2. ConditionClient is on a care plan
    if
  3. Action · MessagesAssign to the account's developer
    then
  4. Action · ChatPost to #care
    then
05 · The running business

Pipeline to launch to care plan, on one system

The deal, the contract, the sitemap, the specs, the client's comments, the QA checklist and the support tickets all belong to one client record. Producers, designers, developers and finance work from the same place.

Projects
Saltmarsh Museum — Collections
Orla Health — Design system
Kiteline Air — Booking flow
Care plans · 41 clients
Sections
Boards
Templates
Workflows
Project · Website build · Sprint 6 of 8Saltmarsh Museum — Collections site
Contract · £64,000Build invoiced#saltmarsh · 8 guestsGo-live flow armed
Build
Collection object templateFolio · spec v3
Search filtersCanvas · flow map
QA
Go-live QAChecklist · 9/14
Redirect mapFiles · v2
Live
Launch milestonePayments · £6,000
Care plan startsCommerce · package
Linked
Saltmarsh MuseumCRM
Sitemap · 38 pagesCanvas
Specs · 12 pagesFolio
#saltmarsh · 8 guestsChat
Contract · £64,000Commerce
A week at Lowtide
  1. FormsPlanner: Kiteline Air, booking flow
  2. CRMGreywater pitch moved to Proposal
  3. CanvasCurator comments on the sitemap
  4. MessagesCare ticket answered in 52 min
  5. ChecklistsOrla Health go-live QA 14/14
  6. PaymentsOrla launch milestone invoiced
  7. CRMNorthgate FC · won · £140,000
14of 14 modules in use
ProjectsFolioCanvasChecklistsFilesCRMMessagesChatFormsProfilesSitesCommercePaymentsFlows
Seats
120 · producers, design, engineering and finance
Guests
Client stakeholders and freelancers, per project
Replaces
HubSpot, Pipedrive, Asana, Miro, Notion, Dropbox, Slack, Zendesk, Typeform, Webflow and Zapier
Next use caseGovernment agencies All use cases

Start with one module. Add the rest as you grow.

Every module works with every other from the day you switch it on, and your data exports whenever you want.

Join the waitlist More use cases