Notes from the work · Tag
One" lives in our company Slack. It answers questions, takes notes, changes facts and files requests in plain words, and every change it makes is recorded in the Hub under the name of the person who asked.
Our request desk now asks for the deadline, the other locations and the files up front, files every request on the location it is about, and stays in sync with the Jira desks our team already works in. Here is what is live, and the one part we have not proven yet.
On a franchise marketing call, "not connected" is the most useful thing a location page can say, as long as it says which kind. Here is how the Hub tells them apart, and why each one is a different job.
Our creative, reporting, market, call center and AI tools all ask the Hub who a client is. Here is how that works, the rules that keep it clean, and what it changes when you tell us something once.
Our first portal was organized around a process. A day later we started again with one page per gym, studio or spa. Here is what that page holds, and why a record beats a workflow.
Every tool our team uses to make, run and report your marketing is one we built, at *.sneeze.it. Here is what each one does, who uses it, and how they all read from a single record.
Book a walkthrough with David Steel. Bring last month's lead count and one location you are worried about.