CRM

What it is

A CRM that does not stop at the word *Won*.

Most sales tools model a pipeline and hand you off at the finish line. The part that actually pays — the thing you sold running for a term, coming to an end, and being sold again — lands in a spreadsheet somebody remembers to open. This app keeps both halves in one place, because they are the same companies.

It is deliberately generic. A product here is whatever you sell for a period: a placement on a board, a plan, a licence, a retainer, a room. If your business is "find someone, agree a term, deliver it, renew it", this is the shape of it.

What you get

Seven tables that already know about each other. Companies, Contacts, What We Sell, Deals, Subscriptions, Activities and Enquiries. A contact belongs to a company; a deal points at a company, a person and a product; a subscription points back at the deal it came out of. Open a company and you see its people, its deals, what it currently has with you, and every call anyone logged.

A pipeline board with two gates. Lanes come from the stage column's own options, so changing the options changes the board. A deal cannot leave Proposal until somebody ticks *Proposal sent*, or leave Negotiation until the signed contract is logged — the card simply is not draggable, with the reason on it.

The board is a view of the table, not a page beside it. Deals opens on the pipeline; the view dropdown above it switches to In play or the full grid, with the same filters and the same search. One sidebar entry, one set of rows — so nobody has to work out which of Pipeline and Deals is the real one. Subscriptions works the same way, opening on Renewals with Ending soonest a click away.

A renewals board that fills itself. Every morning an Automation looks for live subscriptions ending inside 45 days and marks each one Due. That edit wakes a second Flow, which puts the call on whoever owns the subscription. Their answer — *Renewing*, *Still talking*, *Not renewing* — is written straight back onto the row, so the board and the decision are the same fact rather than two that drift.

Discount approval attached to one column. Put a number in Discount on a deal and the approval starts on its own. Ten per cent or under clears itself; more than that goes to a manager on a 24-hour clock. Whatever they decide is written onto the deal, and the deal's own page lists the Runs.

One action for a lead. A salesperson who has just put the phone down clicks New Lead and fills in one form — the person, the company, what they want. On submit the company goes on the books if it is new, the person is filed under it, and the deal opens at New. Nobody types a company into one table and a contact into another, and nobody invents a reference.

A public enquiry form, with a human in front of it. Budget over 25,000 goes to a named person on a four-hour clock; everything else goes to the team queue. A stranger's submission becomes a company only once somebody has read it and qualified it — which is the one thing the internal form skips, because the person filling it in *is* the reviewer.

The pattern worth stealing

State lives in a column on the row, never in whichever Step a Run happens to be sitting on. That is why a deal can slip back from Negotiation to Proposal, why a subscription can be marked Due by a schedule and moved to Renewing by a person, and why none of it needs a Flow to be re-authored. Flows are attached *behind* those columns — one for the discount, one for the renewal — and each writes its answer back onto the row it was about.

Fitting it to your business

• Ad or sponsorship sales: a product is a placement with a capacity, a subscription is the campaign running for its booked term, and the renewal watch is the conversation you currently have too late.
• Retainers and services: a product is the engagement, the term is the contract length.
• Memberships and licences: the renewal board is the whole business.
• Space and equipment: capacity is how many you have; booked units is how many are out.

Rename the tables to your own words, change the select options, and the boards, tiles and Flows follow — they read the columns, not a copy of them.

What it expects from your workspace

Nothing. Owners are picked from your workspace's own users, so there is no shared table to line up first. Four of the five Flows arrive with placeholder assignees — a Sales Lead, a Sales team, a Sales Manager — which you swap for real people before publishing. New Lead needs none: it is open to any member and waits for nobody.