Skip to content

Trust and ownership

You own it. That's not a reassurance, it's the architecture.

The questions founders actually ask before handing over the judgment their business runs on, answered in one place instead of four.

No black box

Same input, same answer. The difference is whether you can read what happened in between.

This is the one we won't move on.

A system that can't explain itself can't be corrected, and a business that can't correct its own rules doesn't own them.

A sealed rule between your input and your answerYour business goes in at the top, a slab marked SEALED sits in the middle, and an answer comes out at the bottom. The rule in the middle can't be read, changed or kept.EVERYONE ELSEYour business goes in?SEALEDAn answer comes out
You can't read the rule, so you can't correct it. When it's wrong you argue with a vendor instead of editing a line, and when the engagement ends the rule leaves with them, because it was only ever inside their thing.
The same shape, with the rule written down in the middleThe same input and the same answer, but the middle holds three named rules, each one a line your team can read and edit: how you price a job, when you walk away, and who gets called first.CHIPYour business goes inHow you price a jobeditWhen you walk awayeditWho gets called firsteditThe same answer comes out
Every rule is a line somebody can read. In your words, in your accounts, editable by anyone on your team. When it's wrong you fix the line. When we're gone it's still there, because it was always yours.

Where everything sits

The asymmetry is the argument.

We hold the work. You hold everything the work produces. That's why stopping isn't a migration, and why nobody has to trust a promise about it.

What we hold, and what you holdEverything CHIP produces lives in your own accounts. If the engagement ends, the system keeps running and nothing has to move.YOUR ACCOUNTSYour documents and decisionsYour CRM and its recordsYour Drive, your storageYour accounts and billingOURSThe build workThe integrations we writeSupport and reviewIf this box disappears,the left side keeps running.

The questions we actually get

In the order they get asked.

What happens if we stop working with you?

Nothing switches off.

The system was built in your accounts, so it keeps running exactly as it did the day before. There's no export step, because nothing was ever held somewhere you'd have to export it from.

Do you host our data?

No. It never leaves your accounts.

Your documents sit in your storage, your records in your CRM, under your own billing and your own access controls. We work inside them the way a contractor works inside your building.

Are we locked into a platform?

There's no platform to be locked into.

What you end up with is your own tools, wired together, plus a structured record of how your business decides. Both of those are readable by a person without us in the room.

Can our team read and change what CHIP knows?

Yes, and they should.

Anyone on your team can read a decision, edit it, and see where it came from. A judgment nobody can inspect is one nobody will trust, and an uninspectable system fails quietly rather than loudly.

Does our information train anything, or reach other clients?

No. Separate accounts, separate bases, no shared pool.

Each client's work sits in their own accounts and their own bases. One client's records are structurally unreachable from another's rather than merely filtered, which is a stronger guarantee than a filter somebody has to keep correct.

What if the audit says we don't need you?

Then it says that, and you keep the map.

That's already happened and it'll happen again. A diagnostic that can only ever conclude yes is a sales document wearing a lab coat.

Who actually does the work?

The person you talk to.

There's no account manager layer between you and whoever's building, which is deliberate and is also why we take on a small number of engagements at a time.

What do you refuse to do?

Three, and none of them are negotiable.

We don't send anything on your behalf without a person approving it, we don't touch a client's money fields in a page meant for their customers, and we don't replace software that already works for you just because we didn't build it.

Still got one we haven't answered?

Ask it directly. If the honest answer is that we aren't the right fit, that's a faster and cheaper thing for both of us to find out now.

Ask usWhat we build