About

Why it exists

We run on Attio, and we kept hitting the same wall: a client asks where things stand, the answer is in the CRM, and there is no way to show them. Attio’s help centre says so directly. Restricting a member to a single list needs their Pro plan, and even then the person can still see every record in the workspace.

So you do one of three things. Export a CSV that is wrong by Thursday. Buy a seat at $99 a month so one client can look at eight records and learn a CRM they never asked for. Or rebuild the whole thing somewhere else and maintain it twice. We did all three, more than once, before deciding to build the missing layer instead.

What we are building

A publishing layer for Attio views. Not a CRM, not an app builder, not a second database. You point a view at a list or a filter, switch on the attributes a viewer should see, lock the link however the situation deserves, and send it. Your viewer needs no account and no seat. Attio stays the source of truth, and we never hold the original of anything.

The whole product is about what a viewer cannot reach. That is why every attribute starts hidden, why publishing shows you the real page before anyone else sees it, and why a viewer’s edit waits for your approval instead of landing in your CRM unread.

How we price it

Never per viewer. A hundred people or ten thousand people opening your view costs the same, on every plan including the free one. Paying per head to let somebody look at a list is the thing you came here to stop doing, so charging for it would be a strange way to sell the fix. You pay for how many views you publish and what you can do with them. The pricing page has the rest.

The free plan is not a trial. One read-only view, up to 500 records, no card, no expiry. If that is all you need, keep it.

What we will not do

• Invent proof. There is no logo wall on this site because there are no logos yet. No testimonials, no usage counts, no “join 4,000 teams”. When something is real and the customer has agreed in writing, it goes up with their name on it.
• Name a customer without written permission. Ever, including as an anonymised case study specific enough to identify.
• Describe the freshness as anything other than the interval it is. We check Attio on a schedule and we quote the schedule. A customer with a stopwatch settles that argument, and we would lose it.
• Claim a certification we do not hold. No SOC 2, no ISO 27001, no penetration test report, and no phrase standing in for one. The security page lists the gaps by name.