Everything that lands on one desk.

Knowing who your members are.

Knowing who your customers are.

Knowing who your supporters are.

A person, and the business they run, are kept once — in the middle of the product, not inside whichever part of it met them first. The company that books a table at your lunch, pays its dues, posts a job on your board and appears in your directory is one member, not four. That single decision is what everything else on this page rests on: there is never a second list to keep in step.

A customer is kept once — in the middle of the product, not inside whichever part of it met them first. The person who asked for a quote, got the invoice, booked the follow-up and opens what you send out is one customer, not four. That single decision is what everything else on this page rests on: there is never a second list to keep in step.

A person, and the firm they belong to, are kept once — in the middle of the product, not inside whichever part of it met them first. The firm on your register, the delegate at your conference, the name on a committee and the subscription you invoice are one member, not four. That single decision is what everything else on this page rests on: there is never a second list to keep in step.

A supporter is kept once — in the middle of the product, not inside whichever part of it met them first. The person who gave last spring, bought a table at the benefit, sits on a committee and gets the newsletter is one supporter, not four. That single decision is what everything else on this page rests on: there is never a second list to keep in step.

Getting paid, and knowing that you were.

Taking the gift, and receipting it.

Dues, event seats, sponsorship and advertising are invoiced from the same records the rest of the job runs on, numbered your way rather than ours. A payment is recorded against the invoice it settles, so “did they pay” is a fact on a screen rather than a search through a drawer.

Jobs, deposits, retainers and repeat work are invoiced from the same records the rest of the job runs on, numbered your way rather than ours. A payment is recorded against the invoice it settles, so “did they pay” is a fact on a screen rather than a search through a drawer.

Subscriptions, conference places, sponsorship and advertising are invoiced from the same records the rest of the job runs on, numbered your way rather than ours. A payment is recorded against the invoice it settles, so “did they pay” is a fact on a screen rather than a search through a drawer.

Gifts, pledges, table seats and sponsorship sit against the same records the rest of the job runs on, numbered your way rather than ours. A payment is recorded against the thing it settles, so “has that come in” is a fact on a screen rather than a search through a drawer.

Filling a room, and billing the room.

Filling the day, and billing the day.

An event is drafted, published, and canceled if it has to be. Booking is open to anyone, closed behind a password, or off entirely. People take a single seat or a whole table, with the names filled in later, and a paid seat becomes an invoice against the same member record — which is what stops the unpaid ones living in somebody’s memory.

An open house, a class, a customer evening: drafted, published, and canceled if it has to be. Booking is open to anyone, closed behind a password, or off entirely. People take a single place or a whole table, and a paid place becomes an invoice against the same customer record — which is what stops the unpaid ones living in somebody’s memory.

A benefit, an open evening, an appeal night: drafted, published, and canceled if it has to be. Booking is open to anyone, closed behind a password, or off entirely. People take a single seat or sponsor a whole table, and a paid seat sits against the same supporter record — which is what stops the unsettled ones living in somebody’s memory.

The website, and the directory on it.

The website, and what is actually on it.

The website, and who is named on it.

Your public site is part of the same product rather than a separate one with a separate login and a separate bill. Pages carry a draft and a published version with a history behind them, so an edit is something you can look at before the town does.

The member directory is not a page anybody maintains. It comes off the member records themselves, which is why it cannot drift away from them. A business can ask to claim its own listing, and your staff decide.

The lists on it — what is coming up, what you are hiring for, who you work with — are not pages anybody maintains. They come off the same records you work on, which is why they cannot drift away from them.

Your supporters page is not a page anybody maintains. It comes off the records themselves, showing only what you allow it to show, which is why it cannot drift away from them or name somebody who asked to stay quiet.

The newsletter, without a second address book.

An issue is written here and sent to everybody, or only to members. Who gets it is worked out at the moment you press send, from the records you already keep — so there is no mailing list to import, clean, or forget to update when somebody lapses.

An issue is written here and sent to everybody, or only to customers. Who gets it is worked out at the moment you press send, from the records you already keep — so there is no mailing list to import, clean, or forget to update when somebody moves on.

An issue is written here and sent to everybody, or only to supporters. Who gets it is worked out at the moment you press send, from the records you already keep — so there is no mailing list to import, clean, or forget to update when somebody stops giving.

A big send runs down its own lane against your own allowance, and one above a certain size waits for a named person to say go. That is not a feature we are proud of inventing — it is there because runaway email has happened.

The things that are bigger than an event.

A golf tournament is not an event; it is a small organization with a roster, a task list, sponsors, a budget somebody is guessing at, and receipts in a shoebox. Workspaces are where that lives — one inside another up to three deep, archived rather than deleted, with thirty days to change your mind.

A trade show stand is not an appointment; it is a small project with a crew, a task list, suppliers, a budget somebody is guessing at, and receipts in a shoebox. Workspaces are where that lives — one inside another up to three deep, archived rather than deleted, with thirty days to change your mind.

An annual conference is not an event; it is a small organization with a committee, a task list, sponsors, a budget somebody is guessing at, and receipts in a shoebox. Workspaces are where that lives — one inside another up to three deep, archived rather than deleted, with thirty days to change your mind.

A spring appeal is not an event; it is a small organization with a committee, a task list, sponsors, a budget somebody is guessing at, and receipts in a shoebox. Workspaces are where that lives — one inside another up to three deep, archived rather than deleted, with thirty days to change your mind.

Money asked for inside one becomes an invoice in the same place as everything else, so a sponsorship does not turn into a private arrangement in somebody’s email.

Letting members do it themselves.

Letting customers do it themselves.

Letting supporters do it themselves.

Members sign in to the same product your staff use, seeing only what is theirs. The same words, the same screen, the same buttons — not a thinner second product built later and looked after worse.

Customers sign in to the same product your staff use, seeing only what is theirs. The same words, the same screen, the same buttons — not a thinner second product built later and looked after worse.

Supporters sign in to the same product your staff use, seeing only what is theirs. The same words, the same screen, the same buttons — not a thinner second product built later and looked after worse.

Answering “how are we doing?” once.

Reporting reads across everything you run, from one place. Membership, money and who turned up are the records the day already runs on, so a board number is something you look at rather than something you build.

Reporting reads across everything you run, from one place. Customers, money and who turned up are the records the day already runs on, so the month’s number is something you look at rather than something you build.

Reporting reads across everything you run, from one place. Giving, money and who turned up are the records the day already runs on, so a board number — or a funder’s — is something you look at rather than build.

What you filtered and what period you asked for live in the address of the page. The report you built is a link, and whoever you send it to opens the same thing you were looking at.