FAQ.

Every piece of work has one fixed price, quoted in writing before it starts, and it does not change once you say yes. We quote after the first conversation, once we know the business and the decision it needs.

The Assessment comes first and is quoted on its own. It is a paid piece of work in its own right, whatever it concludes. If it recommends a build, that is a separate proposal with a fixed scope, a fixed price and an end date, and agreeing with the recommendation does not commit you to it.

The Assessment takes about three weeks and needs eight to twelve hours of your team's time.

A build has its own dates, agreed before it starts, including time running in the business before we measure the result.

Yes. It is where the investment decision gets made, and anything we build is scoped from it.

If the first conversation shows the problem is too small, too early or already covered by a provider you have, we say so, and there is no Assessment.

Those put a tool on each desk, and people use them their own way. What we build does a defined job for the business. It works from shared company knowledge, uses only the connections you have approved, and has limits and approval rules built in.

Getting AI to do a task is one part of it. We build around the company's knowledge, permissions and approval process from the start.

Then that is the answer, and you have it in writing with the reasons.

Not yet, your own team, a provider you already pay, or fixing something else first are all answers we give when the evidence points there.

Only what you have agreed in writing. Anything that would change your systems is drafted first or waits for a person's approval, unless the signed scope allows a narrower action after it has been tested.

Decisions with a consequence, such as money, legal, employment or customer commitments, stay with people. Everything it does is logged, with who approved it.

Only where the agreed work needs it, and you approve each connection. AI processing goes through zero-data-retention provider routes by default, each customer is kept separate, and Kriaka staff have no routine access to private conversations.

Some processing may happen outside New Zealand. If you have a residency or provider requirement, raise it early and we will tell you plainly whether it can be met.

Bryce Galbraith, Kriaka's founder, from the first conversation through the Assessment and into the build.

Larger builds are delivered with a partner team that Kriaka leads.