One standard across every unit you own.

Layer one: each unit answers in its own voice

The same enquiry arrives at all three agencies. Each unit's standing rules are its own — written by that unit, in its words — so the same question gets three different drafts, and every draft waits for that unit's person to approve it.

Hi Amara,

Thanks for reaching out — a booking site with payments is right in our lane, and resort work is some of our favourite.

To be straight with you on cost: full site builds with us start from ₱90,000, and where yours lands depends on the booking engine and payment setup you want. Rather than guess at that in writing, could we take 20 minutes this week to walk through it? I'll bring real examples.

Corva Creative

Hi Amara,

Thank you for the detail — a booking rebuild with payments for a resort group is a meaningful project, and the honest answer is that any figure I gave you now would be a guess dressed up as a quote.

What we do instead is a short discovery call: what you have today, what has to change, and what it is costing you as it stands. After that, any number we put in writing is one we can defend. Would Thursday or Friday morning suit?

Kestrel & Co

Hi Amara,

Got your message — and good timing, we've shipped two booking systems this year.

One thing about how we work: pricing here comes from Miguel, our founder, directly — he scopes every project himself so the number you hear is the number that holds. I've flagged your enquiry to him and his calendar link is below; he keeps mornings free for exactly these calls.

Northreach Digital

Three policies, three voices, one queue each. No head office rewrote anything — and no draft went out until a named person at that unit approved it.

Layer two: the line no unit can cross

Now the message that matters. Contractual, legal, security and compliance questions are caught by a veto layer that is engineering-owned: it is not a setting, no unit can loosen it, and neither can the holding company. The same dangerous enquiry, sent to all three:

Three units, one identical refusal — and that sameness is the product. A portfolio where every unit improvises its own answer to "are you SOC 2 certified?" is a portfolio where one unit eventually says yes in writing. Here, none of them can.

The trail a diligence team actually reads

Every step above is recorded per workspace — the AI draft, who approved it, what they changed, when it was sent, and every hold with its reason. Each unit's owner can export their complete trail as JSON in one click, without asking us. That is what "one standard across the portfolio" looks like when someone checks.

Drafted

Every AI draft is recorded with the workspace rules that shaped it.

Approved

Every send names the person who approved that specific message — edits included.

Held

Every veto is recorded with its class. A hold is a decision, and it stays on the record.

What this page is, honestly

A demonstration with fictional companies, because we launched recently and have no customers to show you — our home page says the same. The two-layer mechanism is the real, shipped product: per-unit standing rules, an approval gate on every drafted reply, and a veto layer no tenant can switch off, all asserted by our test suite rather than promised in a policy.

Running more than one unit and want to see it on your own traffic? Send us the last three enquiries one of your units received and we'll send back what the system would have drafted — free, before anything is paid.

The whole system → · Where your data lives →