Solutions
Agencies
For teams running stores on behalf of clients.
What you have
Several clients, each expecting a store, a product decision and a defensible reason for both.
What you want
To run those engagements without inventing the reasoning yourself, and to hand a client evidence rather than an opinion.
What is in the way
FlowFinds has no shared workspace, no roles and no seat billing. An agency runs it as a set of separate accounts, and should decide up front who owns each one.
Read this part first
There is no single sign-on, no shared workspace with roles and permissions, no organisation-level billing across seats, and no audit export. We are not listing those as forthcoming, because we do not have dates for them. What exists today is one account per email address, and an account is its email address: clearing a cookie does not mint a second identity or a second allowance, and sign-in is an emailed single-use link with no password to store.
That shapes the engagement more than any feature on this page. Decide before you start whether each client account is held by the client or by you, because it determines who keeps the claim, the store and the customer records when the engagement ends.
What FlowFinds gives an agency that it does not give an operator
Nothing, and that is the point. The value to an agency is not extra capability — it is that every recommendation arrives with its own provenance already attached, in a form you can put in front of a client without re-deriving it.
- A product choice you can defend line by line. Three legs, each on its own dated sources, each showing the claim, the source URL and the date. A client asking “why this product” gets rows, not a narrative.
- A section order that explains itself. The store engine emits an order rationale — one entry per section saying why it sits where it does — and a section that cannot cite the evidence row justifying its position does not ship. That is a build gate, so the artefact you show a client cannot have been written after the fact.
- A pass bar stated before the spend. The ad artefact carries click-through at or above three per cent and cost per click below one euro, written before any money moves. An agency that agrees the bar with a client in advance is reporting against a criterion rather than negotiating one afterwards.
- A rejected alternative on every edit. A proposed change cites the dated row that justifies it, names the alternative it rejected and why, and marks whether it can be put back. Nothing applies until it is accepted: a proposal is created with an empty applied-at field by construction.
What you do
| Step | Who acts | What exists afterwards |
|---|---|---|
| Agree who holds the account and the claim | You | An unambiguous owner for the exclusivity and the records |
| Create the client account against its own email address | You | One tenant, one allowance, one sign-in link |
| Work the feed and claim on the client's behalf | You | An exclusive claim held by that account, not by your agency |
| Generate the store and read the order rationale | FlowFinds | A storefront plus a written reason per section, ready to present |
| Present the artefact and the pass bar to the client | You | An agreed criterion before any spend |
| Run the test in the client's own ads account | You | A measured result against the criterion you agreed |
| Hand over the account | You | The client signs in with their own email; nothing is transferred, because nothing was pooled |
What it costs
One subscription per account, on the same four tiers everyone else uses. There is no agency rate and no reseller margin. The Max tiers exist for volume — five and twenty times the reference allowance, metered per feature so heavy use of the website editor does not exhaust the find engine — and the full ladder is on pricing.
The funded first launch belongs to the account, not to the agency: the ten euros is unconditional per account and is held as a real balance, credited on a real event. It is not a pool you can draw against across clients.
Honest limits
- No shared workspace, no roles or permissions, no organisation-level billing, no audit export, and no contractual service level beyond our published availability commitment. We hold no security certification.
- Each account sees only its own claims. Order lookups are founder-scoped by construction and have no unscoped form, so there is no cross-client view — for you either.
- Exclusivity is global. Two of your clients cannot hold the same product, and a product claimed by an unrelated founder is not available to any of them.
- The API exists and is documented, but it does not offer an agency-level abstraction over multiple accounts.
- We do not white-label. The reasoning, the refusals and the provenance are ours and are visible as such.
If any of the missing pieces are blocking, that is a conversation rather than a signup: write to [email protected], or see enterprise for the diligence material that does exist. The API is documented under documentation.