A fair, practical way to work together.

Start with the work

We sit with the people doing the job, map the real inputs, rules, exceptions, systems, and approval points, then propose the smallest useful scope. Each module has a fixed build price, a named owner, and an acceptance test using real work. You accept the module before Briu invoices the build.

What each side owns

You own your data, names, numbers, files, marks, and business-specific process material. Your data is exportable at any time and deleted on request, subject only to records Briu must retain by law.

Briu owns its software and the module configuration, including reusable workflow patterns, cell framework, templates, tools, generalized improvements, and know-how. While you are a customer, you receive a license to use the named module for your own business. The license does not allow resale, rebranding, sublicensing, or use for another organization. A client-owned code handoff is available only when an order form prices and identifies it separately.

Confidential does not mean exclusive

Your data, people, numbers, source material, and process specifics stay confidential and never become another customer’s material. Briu may keep using general methods, code, workflow patterns, and lessons that reveal none of those specifics. No engagement is exclusive unless an order form names the protected field, duration, and price.

Continuity by default

For a managed module, Briu keeps an encrypted, release-specific continuity bundle in a private repository you can read. It contains the customer configuration, required reusable Worker files, a checksum, and a practical re-hosting guide, but no secret values or customer data. You can open a release request there at any time. The key releases after 30 days unless Briu contests the request. Release applies if Briu ceases operating, gives notice without a workable transition, leaves a critical accepted defect unfixed for 30 days, or Lucas dies or becomes incapacitated. Cancellation alone is not a release condition. Paid third-party escrow remains available as an optional priced term.

Module price plus module care

The build and ongoing care are separate. The fixed module price covers the agreed implementation and acceptance. Monthly module care starts only after acceptance and keeps the accepted service operating: hosting, credentials, access help, monitoring, delivery checks where included, compatibility work, defect repair, ordinary questions, and reasonable small changes inside the agreed workflow. Briu acknowledges normal requests by the next business day. Care is not 24/7 support, an uptime guarantee, human operation of the workflow, or unlimited development unless the order form says otherwise. New workflows, connectors, decision rules, and substantial changes receive a written quote before work begins. Third-party charges stay visible and follow the order form.

Data and service providers

We minimize the data each workflow uses and name the systems involved. These may include Cloudflare, Resend, Salesforce, an AI provider, or systems you already control. The order form and any required data-processing addendum identify the actual providers, data classes, retention, access, and human approvals for your module.

A workable exit

When an engagement ends, you receive a practical data export, an audit-log export, and up to 30 days of transition help. Briu deletes customer data on request after required retention periods. The ordinary hosted license ends with care, while a valid continuity release, paid escrow release, or separately purchased handoff follows its written terms. Credentials and customer-owned accounts return to customer control.