Before you begin.

Teams whose problem is data that does not agree with itself: manuals in several revisions, a business spread across many tools, records that contradict each other. You need approved sources, a clear question and someone who can judge the answers. Industrial and operations teams are the most common, and we also work with specialists who run their work through many tools.

It is free and takes about thirty minutes. We talk through the problem, who has it, what data exists and what would count as fixed. You leave knowing whether a diagnostic makes sense.

A fixed price, agreed in writing, never more than $3,000. You get a written finding: the data you have, the gaps, how a solution would be judged, and a recommendation on what to build. Sometimes the recommendation is to build nothing, and the finding says why.

Yes. It is a separate decision with its own scope and price. Nothing in the diagnostic commits you to it.

Before a build starts we agree on real questions, the sources that count and what a correct answer looks like. The build is judged against those: right source, right revision, honest unanswered cases, and how much reviewer time it saves. Targets go in the scope so both sides are measuring the same thing.

Yes. Bilingual search and answers are a normal part of the work. The scope names the controlling language for each document and who reviews specialist terms. A translated answer points back to the approved original.

On your hardware, on ours, or with a hosted provider. Local-first is the default preference. The scope says exactly what runs where and which providers, if any, touch your data.

Your data stays yours. A one-time build is delivered with its source code. A hosted or licensed system has its own usage terms and may include components Celaya keeps. The agreement lists deliverables, reusable parts and any third-party licenses.

Whatever the scope says: handover, documentation, review milestones and any maintenance. Hosted systems carry a recurring fee, and infrastructure costs are stated separately. Response times and change requests are agreed in writing.

For a build, you already have the code and the documentation. For a hosted system, the agreement sets export formats, the transition work and how long access and data are kept. Both are settled before work starts, not at the end.