Skip to main content

Preface

What this is​

This is the canonical guide to Fyndow — the operating system for service businesses. It explains what Fyndow is, who it is for, how its parts fit together, and how it behaves end to end. Whether you are a product person checking what "done" means for a feature, an operator who needs to understand how money and trust move through the system, or simply evaluating the platform, this is meant to be the place you start — and, for most questions, the place you finish.

Fyndow is built around a single idea: a service business should be able to run everything — bookings, quotes, invoices, payments, clients, a marketplace storefront, community, reputation, and an AI assistant that does real work — in one place, instead of stitching together half a dozen disconnected tools. It is available as a web application and a mobile app.

What reading this should leave you knowing​

After working through this guide, you should be able to:

  • Explain the product — who Fyndow serves (providers, customers, and organizations), what problem it solves, and why it is structured the way it is. See Foundations and The Product.
  • Trace the core flows — how a booking, an order, a quote, or an invoice moves from creation to completion, including the state machines that govern them. See How It Works.
  • Understand the money and trust model — how payments, escrow, fees, payouts, and refunds work, and how credentials, reviews, and reputation combine into a trust signal. See Money & Trust.
  • Work with the AI assistant — how Fyndow's assistant uses confirmation-gated tools to do real work on a provider's behalf. See The AI Assistant.

The fastest way to get oriented is the next chapter, How to Read This Book. If you encounter an unfamiliar term, the Terminology & Conventions chapter — and the full Glossary — will define it.

A note on accuracy​

Fyndow is a living system under active development. This guide favors accuracy over fluency: every claim about behavior is meant to be traceable to how the product actually works. Some areas are complete, some are in progress, and a few are deliberately deferred. Where that is the case, the chapters mark it rather than smoothing over it.