Is this a CRM?
Not a replacement for one. It is enough pipeline to compose from, sitting next to the intelligence that makes the composing worth doing. If you run a real sales organization, keep your CRM.
Who you are talking to, where each conversation stands and what you owe them next, kept beside the knowledge you would answer them with.
Learn next: Case Studies · Workspaces · Organizational Intelligence · Personas · Expressions
A light record of who you are selling to and where each conversation stands, sitting in the same place as the knowledge you would draw on to move it forward. Each customer carries a stage, where they came from, and the one thing you owe them next with a day against it. From the customer you start the next piece of work, already knowing who it is for.
Everything you argue with lives beside it, under Foundation: the market you sell into and who you are up against, what you sell, the people you sell to, and the proof you can put in front of them.
Most sales tooling knows the state of the relationship and nothing about the substance. Most knowledge tooling is the other way round. The consequence is familiar: the person who has to send something is the person who has to go and find what to say, from scratch, at the moment they are already late.
Holding both in one place means the next deck for a customer starts from what you already learned about them, and the proof you put in it is the proof your organization actually holds on file. Nobody has to work from a half-remembered version of it.
A customer is a real place in the platform: what you have read for them stays theirs, the work you make for them files itself under them, and the projects you have run for them are listed on the record. On top of that sits the thin part: a stage from first contact to active or lost (Lead, Contacted, Demo, Proposal sent, Pilot, Active, Dormant/Lost), how they found you, and a next step with a date. Proposal sent is the stage between a demo and a yes: the offer is out and you are waiting for an answer. The stage names follow the interface language: in Dutch, Proposal sent reads Offerte. Nothing writes a commitment on your behalf. The stage offers a suggestion for the next step; you accept it or you type your own, because a step nobody typed is a step nobody owes.
The Customers page lists who you work for. It opens on how many customers you have, what is Waiting for you across them, how many profiles still miss answers under Profiles to complete, and, once you keep a pipeline, the Follow-ups due this week and how many are overdue. Each row says the customer's industry, how many of their decks wait for your review with a button that opens the first by its code, their stage and when their next step is due, how much of their profile is captured, and what you owe them. Search, Industry, and Stage and Follow-up once any customer has a stage or a next step, narrow the list. One click opens the customer.
A customer has one page. It is their workspace: their name with Customer and their industry above it, their logo beside it, and Who they are under it. Below are tabs: Projects run for them, Files made for them, What Gyrium knows about them, the Sources read for them, the Journal of every note and stage change, and Details: name, type, industry, sectors, language and market, the contact, the logo, and archiving. Edit details opens Details; Add a source opens Sources ready to upload. Where your organization keeps a pipeline, Relationship sits under Who they are: the stage, the next step and when it is due, and Done, clear it once it is done.
Each customer has a profile. What they offer, where they operate, their market, who they sell to, the problems they face, their competitors and what they stand for, each field showing where it came from and when. It is read in the customer's own language and grounds every piece you make for them, so nobody retypes it into a brief. Answer it yourself fills it in by hand, at no cost: what you type is saved as the customer's facts the moment you choose Save profile. Or read it from Their website, Pasted text or A document, and Gyrium fills the answers. Changing a customer's language or market asks first, because the work made for them follows it. A customer also carries its sectors, the industries it works in, and every piece made for it draws on what you hold about those.
What you sell with is edited in one place. Your category, your competitors, what sets you apart and where the market is going are records under Foundation, in Selling, alongside your offerings, your personas and your proof. They are typed in and they are yours. Generation reads that same set, so what a proposal says about your position is what you wrote there.
A finished project writes its own case study, from its own record, into that proof. That is the one piece of composition this surface does, and it has its own page.
Not a replacement for one. It is enough pipeline to compose from, sitting next to the intelligence that makes the composing worth doing. If you run a real sales organization, keep your CRM.
No, and that is on purpose. You state your category, your competitors, your differentiators and where you think the market is going, in Foundation. What the platform does is compose from them, consistently, in every piece, by everyone. A position nobody in your company stated is not a position worth repeating a hundred times.
The project record, when the project finishes. Not from a blank page and not from memory.
You can filter and sort your customers by stage, by where they came from and by what is overdue. There is no reporting beyond that, deliberately.
No integration with an external CRM and no email sync: what is here is typed here. There is no forecasting and no reporting beyond filtering the customer list. Nothing proposes a competitor, a differentiator or a market trend for you: those fields are typed in Foundation, by you. This is deliberately a thin layer, and it is the layer that stops a proposal being written from a blank page.
Turn attention into a known contact
Win the business
Foundation, collection, customer, project or campaign, and how to tell which.
Write it once for one customer. Sell it to the next twenty without pasting anything.
A finished project writes its own case study, from its own record, into the proof the next proposal quotes.
A workspace is one initiative: a project, a customer or a campaign, with everything made for it gathering there on its own.
The memory of your organization. Everything it knows, captured as sourced facts, structured by a curated taxonomy, and available to everything you make.
Who you are talking to, as an audience and the people inside it, held as part of your intelligence so strategy is set against someone real.
The work you actually ship. An Expression is a rendered view of your intelligence, in your brand.
The pilot takes a small number of organizations at a time. Bring what you already have.