Fewer, better surfaces
Every new screen has to earn its place. If a feature can be a setting, it stays a setting.
Sicurs started inside an agency, on a Friday, halfway through rebuilding the same client report for the ninth month running.
The team behind Sicurs spent years running search programmes for small businesses and mid-market brands. The work itself was fine. The scaffolding around it was not: briefs in one doc, research in a second, tracking in a sheet, reporting rebuilt by hand, and a folder structure only one person understood.
We tried the obvious fixes — stricter naming, more templates, a wiki. They lasted about a quarter. The problem was not discipline. It was that no single tool held the shape of the work, so the shape lived in people's heads.
So we started building one. Sicurs is that workspace: opinionated about structure, quiet about everything else, and built so a new team member can pick up a client on day one without a two-hour handover call.
Four rules that decide what we build and, more often, what we leave out.
Every new screen has to earn its place. If a feature can be a setting, it stays a setting.
Export on every plan, in open formats. We never make leaving harder than joining.
Pages load fast on a phone on a bad connection, or we do not ship them.
Roadmap decisions come from calls with people doing the work, not from a growth dashboard.
A rough workspace built for one agency's own client load. Ugly, but it stopped the file hunting.
Twelve teams asked for access. We rewrote it properly, added roles, sharing and version history.
Opening in batches so support stays fast and every early team gets a real onboarding call.
Everyone here has run client work. Replace these cards with your real team before launch.
Product direction and search strategy.
Platform, performance and the boring reliability work.
Interface, design system and documentation.
Onboarding, migrations and answering you quickly.
Early access teams get direct input on the roadmap and a founder-led onboarding call.