The Business Toolkit
For a service provider, Fyndow is not a listing site — it is the software that runs the back office. The business toolkit is the set of operational capabilities a provider uses to quote work, schedule it, deliver it, invoice it, collect payment, and keep the relationship warm afterwards. Rather than count "tools," it's easier to think in capabilities: each one is a self-contained part of the platform with its own validated API and data model, and together they cover the whole arc of running a service business.
This chapter walks the toolkit by capability. Almost everything here is provider-scoped: it requires the provider role and is bound to a specific business (see Roles & The Permission Model). Most providers drive these capabilities through the AI assistant rather than by clicking through forms, but the underlying functionality is identical either way.
The Toolkit at a Glance
The capabilities form a loop. You win the work, get paid for it, keep the relationship, sell alongside it, and learn from the whole thing — then promote what's next.
| Capability | What it does |
|---|---|
| Service listings | Define what you sell and how it's priced |
| Scheduling | Availability, bookings, reminders |
| Quoting | Itemized estimates that convert to invoices |
| Invoicing | Bills, payment tracking, overdue handling |
| Payments | Connected payouts, escrow, milestones, wallet |
| Client management | A provider-scoped CRM |
| Messaging | Job-tied real-time chat |
| Notifications | Multi-channel alerts and preferences |
| Products & orders | Sell physical and digital goods |
| Inventory | Stock tracking and low-stock alerts |
| Portfolio | Showcase past work |
| Reporting | Revenue, jobs, completion rate, cash flow |
| Follow-ups | Automated reminders and re-engagement |
| Credentials & reputation | Verification, mutual reviews, trust score |
| Happenings | Time-boxed promotion of events, sales, and your brand |
| Multi-business | Run several businesses from one account |
Products and orders are covered in depth in The Marketplace; credentials, reviews, and reputation in Trust & Reputation; and Happenings in Happenings. The rest are detailed below.
Service Listings
A service is a single thing a business offers. Each service belongs to a business, has a category, and carries one of four pricing models:
| Pricing type | Meaning |
|---|---|
| Fixed | A flat price |
| Hourly | Billed per hour |
| Starting at | A "from" price; final cost varies |
| Quote | No published price — the customer requests a quote |
A service also stores an optional duration, which feeds scheduling, and an active flag. Customers see only active services; the owner sees inactive ones too. All prices on Fyndow are in Canadian dollars.
Scheduling
Scheduling turns a service into a booked appointment. The provider defines availability — a timezone-aware set of working windows for each day of the week, plus any blocked-off dates. A day with no windows is treated as closed. Every booking is checked against this availability before it's created, so a customer can never book outside a provider's working hours.
A booking moves through a small state machine:
The platform reacts to status changes automatically:
- confirmed → a confirmation goes to the customer, and a calendar event is created if Google Calendar is connected.
- completed → a review request is triggered after a short delay.
- cancelled → a refund is processed if a payment exists and the cancellation falls within the policy window, and any calendar event is removed.
Reminder notifications go out ahead of the appointment via scheduled background jobs. The customer-facing booking flow is detailed in The Marketplace.
Quoting
A quote is an itemized estimate sent from provider to customer. It carries line items (description, quantity, unit price), a subtotal, tax, total, optional notes, and an expiry date. Its lifecycle:
draft → sent → viewed → accepted → declined → expired
The customer is notified when a quote is sent and can accept or decline in-app. The key move is conversion: an accepted quote becomes an invoice, carrying over its line items and the client reference. Because that conversion touches several records at once, it runs as a single all-or-nothing operation, so no half-finished state is ever left behind. Quotes that pass their expiry are swept to expired automatically.
Invoicing
An invoice is the bill. It can be generated from an accepted quote or created standalone. It has line items, a subtotal, tax, total, a due date, an auto-generated invoice number, and a status:
draft → sent → viewed → paid → overdue → cancelled
Invoicing is wired tightly to payments and to automation:
- Invoices past their due date without full payment are moved to overdue automatically, and reminders can be fired.
- When payment is received, the invoice flips to paid, a receipt notification is sent, and — if the business has its accounting integration connected with auto-export enabled — a sales receipt is posted to the accounting system.
- Reminder history is tracked so the same nudge is never sent twice.
Payments
Providers are paid into their own connected payment account. Fyndow collects the customer's payment, then routes the balance to the provider, less a transparent platform fee. A payment record links to the invoice, order, or booking it settles.
Three payment types are supported:
| Type | Behaviour |
|---|---|
| Direct | Charge now, pay the provider on success |
| Escrow | Funds are held until the job is marked complete, then released — protecting the customer; they auto-release after a hold window if there's no dispute |
| Milestone | A separate held charge per phase of a larger job, released as each phase completes |
Escrow and payout timing exist as buyer and seller protection: the customer knows their money isn't gone until the work is done, and the provider knows the funds are committed before they start. A provider's earnings accumulate in a wallet with available and pending balances, and every movement of money is written to a ledger. The full story — how providers get paid, the platform fee, refunds, and payout timing — is in How Providers Get Paid, with refunds and cancellations in Refunds & Cancellations.
Client Management
The clients capability is the provider's CRM. Each client record links a provider to a customer they've transacted with and aggregates total jobs, total revenue, and the last interaction date. Providers can:
- view a paginated, searchable, filterable list of all their clients,
- open a client detail that pulls together that client's bookings, quotes, invoices, and message threads,
- add freeform notes (site-access instructions, preferences),
- apply custom tags ("VIP", "residential", "commercial") and filter by them.
Client data is strictly scoped: a provider sees only clients they've actually interacted with, enforced beneath the role check.
Messaging
Messaging is real-time, job-tied chat. A conversation is usually anchored to a booking or order, so the thread always has context. Messages are persisted, support read receipts, and feed the response-time tracking that flows into a provider's reputation. New messages are delivered live to both parties. Providers see all their conversations from the dashboard; customers see the thread attached to each booking or order.
Notifications
Notifications are the platform's nervous system. Every significant event — booking confirmed, invoice paid, quote sent, new message, review received, community reply, a followed business posting a Happening — can become a notification. Notifications are always stored in-app and can additionally be delivered over multiple channels:
in-app, push, email, SMS, WhatsApp, Telegram
Each user controls per-event-type preferences for which channels fire for which events, plus push delivery on mobile. External channels are notification-only — no business action is ever performed over SMS or WhatsApp, and every external message links back to the app. The dispatch logic and per-event policy are covered in Notifications & Digests.
Follow-ups
Follow-ups keep relationships from going cold without the provider lifting a finger. The platform can automatically send payment reminders, review requests, re-engagement nudges for clients who've gone quiet, and credential-renewal reminders — each scoped to a business and a recipient, and each tracked so the same reminder isn't repeated. This is the connective tissue between getting paid, earning reviews, and bringing past customers back.
Products & Orders
Beyond services, a business can sell physical or digital goods with a cart, checkout, and a fulfillment state machine. Stock-managed products draw down inventory as orders are placed. The full ordering experience is covered in The Marketplace.
Inventory
Inventory tracks stock for products that need it: a stock count, a low-stock threshold, and a status of in stock / limited / out of stock. When stock drops below the threshold, the provider is alerted so they can restock before they sell something they can't deliver.
Portfolio
The portfolio is an image-based showcase of past work on the business page. Items are ordered, and a portfolio item can be tied to the booking that produced it — turning completed jobs into proof of quality that future customers can browse.
Reporting
Reporting is a business dashboard that aggregates the numbers a provider actually needs: revenue, job count, completion rate, cash flow, and review trends over time. It turns the day-to-day activity flowing through every other capability into a picture of how the business is doing.
Credentials & Reputation
Trust is its own capability. Providers upload credentials (licenses, insurance, certifications) for verification, earn mutual reviews tied to real completed transactions, and accumulate community endorsements from peers and the communities they belong to. These fold into a composite reputation score and a set of trust badges customers read at a glance. The whole model — verification, mutual reviews, endorsements, and the badge tiers — is detailed in Trust & Reputation.
Happenings
When a provider has something to announce — a weekend sale, a class, a grand opening, a seasonal promotion — they reach for Happenings: time-boxed posts that surface while they're relevant and quietly retire when their window closes. A business can post a promotion (a sale or special on one of its offerings) or an ad (broad brand awareness), in either a ready-made flyer or a composed card. Posting to a community the business belongs to is free and immediate; reaching the wider public is a paid, reviewed step. Happenings are the toolkit's promotion engine — the way a provider turns "we have capacity this weekend" into customers walking through the door. The feature is covered in full in Happenings, and what public reach costs is in Paying for Reach.
Connected Integrations
The toolkit doesn't ask a provider to abandon the tools they already use. Fyndow connects to:
- Google Calendar — confirmed bookings appear on the provider's calendar, and reschedules and cancellations keep it in sync.
- Accounting export — paid invoices can post automatically as sales receipts to a connected accounting system, so the books stay current without double entry.
- Payments — collection and payouts run through a connected payment account, so money lands where the provider already banks.
- Messaging channels — notifications can reach providers and customers on the channels they actually check, while business actions stay in the app.
These are summarized in Integrations & Channels.
Multi-Business Management
Because one owner can be linked to any number of businesses, a single provider account can run several at once — each with its own page, services, products, clients, bookings, invoices, availability, and financials. The apps offer a business selector, and every business-bound query is scoped to the selected business. The structural details are in Roles & The Permission Model.
Taken together, these capabilities mean a provider can run an entire service business — list, quote, schedule, deliver, invoice, collect, follow up, and promote — without leaving Fyndow, and increasingly without touching a form at all, because the AI assistant can drive every one of them on the provider's behalf.