TERRANES

Field notes

What we decided while building this, and why. Written from the decision record rather than from a content calendar.

We built seat packs, then took them out again

Buying capacity in fives is cheaper per seat, which is what makes a pack worth buying. It also meant our pricing page had to say <em>our minimum is five</em> — and seat minimums are the single practice the research says buyers most resent. The packaging discount was worth less than the sentence it cost us.

Attribution is the record. Throughput is surveillance.

A delivery record that does not say who released a drawing is not a record. A record that counts how many drawings each person released is a monitoring system. The line between them is one column, and the reason it is published rather than promised is that a site engineer has good cause to assume the second thing.

Our sub-processor list names an AI provider, and that surprises people

One feature calls a model: the prose around a status report, when someone asks for it on that report. What leaves is the report’s own figures and task titles — never comment bodies, file text, stakeholder notes or budget lines. That last list is asserted by a test against the payload, because a sentence in a document is not a boundary.

Non-payment should mean read-only, not a locked door

Every screen loads, every export works, nothing is deleted. It is the only version of “your data is yours” that means anything, and it costs us the leverage that an invoice normally buys — which is the point. Here is how it is enforced, and the one place billing state is allowed to touch the database.


There are none yet, and we are not going to invent any.

Terranes is pre-launch. A case study written before a customer exists is a short story, and the buyers this is built for check.

When there are customers, what appears here will name the company, the person who ran the project, and the figure that changed — hours lost to re-explaining, on-time delivery across the portfolio, time for a new joiner to be productive, claims won or avoided. Anything we cannot attribute to a named person at a named company will not be published as a case study.

Until then, the honest substitute is a walkthrough on your own spreadsheet.

Bring your projects. We migrate the first one free.

You invite us into that one project as a guest, we run the import on your own spreadsheet, and you remove us once it is in. About forty minutes — and you keep the imported project either way.