Built for the agency, not for the client work#
Every tool a digital agency buys is aimed at the client work: the campaigns, the deliverables, the reporting. The agency itself runs on something else. A spreadsheet for expenses, a shared document listing who has which login, one board for the dev team and another for sales, and a founder who is the integration between all of them.
ROIkeep is the other half. One product, four applications, one sign-on, and it runs the agency: who works here and what they can reach, what the team is working on, where the next deal comes from, and what was spent. It is not a marketing stack you resell to clients.
Built for digital agencies of roughly 5 to 50 people.
ROIkeep is in alpha and sold through conversation. Tell us how your agency runs today, and we will walk you through it against that.
What each application does#
The hub#
One account per person reaches all four applications. Joining is by invite, and there is no open sign-up.
Removing a person is one action. It bans them from every connected application, ends their active sessions, and writes an audit entry.
People records sit behind the same login: department, job title, employment details, and the documents attached to each person. Attendance runs there too, with clock in and out, leave an admin approves, and a month view per person.
Physical keys are tracked the same way, so the answer to which office key is with which person right now is a page rather than a thread in a group chat.
Moving in is done for you, and you see it before it happens. A password-manager export shows exactly what would be created before anything is written, and the import lands as one change or not at all.
When one person needs one credential, you send that credential on its own, with an expiry. It is destroyed the moment it is opened, revoked, or expired, and you can see whether it was collected.
Command and Control#
One codebase renders as two boards, chosen per member: an engineering board with Initiatives, Teams, Projects, and Tickets, and a marketing and sales board with Sagas, Chapters, and Tickets. Both sit on the same tables, and data never crosses between them.
Tickets move through seven statuses and carry exactly one assignee. A ticket blocked by another cannot change status until the blocker clears, and the server refuses the change rather than the interface hiding it.
Every ticket surface has a kanban board and a list view sharing the same filters. Any drop or priority change undoes with Ctrl+Z, up to a hundred steps back.
Recurring tickets spawn on a cadence you set, from every day to every year, so retainer work is not re-created by hand each month.
Lead Central#
Outbound campaigns are built from a lead import that is safe to re-run. Import the same file twice and leads update in place instead of duplicating.
Cold calling gets a 15-stage status set written for a rep working a phone list, from Attempting Contact through Decision Maker Identified and Demo Booked to Won, Lost, or Do Not Call, with each stage defined inside the dropdown.
Upwork, Fiverr, and LinkedIn are separate pipelines with their own statuses, not one generic pipeline bent to fit three sources. Platform leads carry meeting dates, offer values, and a conclusion you are forced to pick when you close one.
Gig analytics are read from a screenshot. A vision model pulls impressions, clicks, orders, and cancellation rate out of the image, and every extracted value is shown for correction before anything saves.
Upwork connect balances, monthly budgets, and low-balance thresholds are tracked per profile. Balances are typed in. There is no Upwork sync, and we will not pretend otherwise.
The expense tracker#
A voucher cannot be saved without a receipt attached. One to three per entry, by file picker, drag and drop, or the camera on a phone.
Categories are capped at six, enforced by the server, and each member sees only the categories assigned to them.
Every entry is typed in. There is no import, no receipt scanning, and no bookkeeping. This is the record of what the agency spent, and it is nothing else.
How the four hold together#
The hub is one of the four applications, and it is also the layer the other three sit behind. Command and Control, Lead Central, and the expense tracker each sign in against it and take role and department from it, so none of them keeps a user list of its own.
That is what turns offboarding into one action. Remove someone in the hub and they are banned from every connected application, their sessions end, and an audit entry is written. There is no list of accounts to chase on somebody's last day, because there is one list.
Proof#
Silverthread Labs runs its own company on ROIkeep.
How ROIkeep is bought#
ROIkeep is a productized service, not software-led SaaS. There is no self-serve sign-up and no checkout. You talk to us, we look at how your agency runs today, and the number comes out of that conversation.
Three plans sit on one ladder: Essential, Private, and Custom. Every plan ships every feature, so the plan decides where your instance runs and how the price is set, never what the software does. Nothing is priced per user, on any plan.
Questions agency principals ask#
Is this something we resell to our clients?
No. ROIkeep runs your own business: your people and their access, your work, your pipeline, your expenses. It is not a marketing stack you put a logo on.
We already run a project tool. Does this replace it?
Command and Control is a full work management application, so it can. What it adds is that the board, the login, the pipeline, and the expense record are the same account, and ending that account ends all of them. If a project tool is the only thing you would move, the argument is thinner, and we will say so on the call rather than after it.
What does alpha mean here?
The product runs every day and it is not finished. We take agencies on through conversation rather than a sign-up form, and we name what is missing instead of routing around it. Two of those gaps are already on this page: the connect balance is typed in, and expenses have no import.
How does someone get access, and how does it end?
Access starts with an invite from the hub, because there is no open sign-up. It ends in one action that bans the person from every connected application, ends their sessions, and writes an audit entry.
Can we see it working before we decide?
Yes. We will walk you through it against your own way of working. We are not promising a date on a web page, because the conversation sets one.
Talk to us about ROIkeep#
Alpha, sold through conversation, and nothing on this page to buy. Tell us how the agency runs today.