HOW WE WORK · FROM WORKFLOW TO OPERATION
From the first conversation to a workflow your team runs.
A clear path from one real workflow to production, with your team involved at each decision.
THE PATH INTO PRODUCTION
Know what happens next.
01 / Briefing
Briefing
- What we do
- Forty-five minutes with a principal. We listen to one workflow and one constraint and say if bolde. is not the right fit.
- What you provide
- Describe the workflow and the systems it touches. Do not send documents before a mutual NDA.
- What you have
- A decision about whether to define a deployment scope together.
02 / Configuration
Configuration
- What we do
- We configure bolde. for that workflow and your security level. We write the scope and acceptance criteria before the Build.
- What you provide
- Choose the security level, give access to the right system owners, and agree on useful results.
- What you have
- A configured deployment, with its scope and acceptance criteria agreed.
03 / Build
Build
- What we do
- Deployment Engineers connect bolde. to your systems and build the agents against the acceptance criteria agreed in configuration.
- What you provide
- Provide scoped system access, representative examples and the people who will review the work.
- What you have
- A workflow ready for your team to evaluate in its own environment.
04 / Acceptance
Acceptance
- What we do
- We resolve gaps against the agreed criteria. The workflow goes live when it meets them.
- What you provide
- Test the workflow on your own examples and record your acceptance decision.
- What you have
- An accepted workflow your team can run in production.
05 / Operation
Operation
- What we do
- We run and improve the deployment and add approved workflows under the same agreement.
- What you provide
- Name the owner for each workflow and approve changes to its scope or rules.
- What you have
- A working deployment with an accountable operating path.
Your agreement is designed to cover configuration, build and subscription, with your security level in a written schedule. Planned
AFTER THE BRIEFING
After the Briefing — typical next steps
| Step | Who takes part | What you leave with |
|---|---|---|
| Briefing | You and a principal | Fit or no fit, said in the meeting. |
| Phase 0 proposal walk-through | You, your counsel or compliance lead, and your IT provider | A proposed scope, security level and agreement to review. |
| Decision | You | Sign or stop. |
ACCEPTANCE
Agree on useful before we build.
Scope and acceptance criteria are written before the Build. Your team evaluates the workflow on its own examples, and it goes live when it meets those criteria.
BEFORE YOU SIGN
Questions to settle before signing
Deployment-specific; review the proposed agreement.
- Implementation scope
- When billing starts
- Separate usage costs
- What changes the fee
- What happens if acceptance isn't met
- Renewal and exit terms
AFTER GO-LIVE
The work continues in operation.
We operate and improve the deployment. Additional workflows are agreed under the same agreement. Product releases and availability are recorded in the bolde. product catalogue; the site’s release-delivery claim remains Planned in the Trust Center until its owner verifies the record.
STRAIGHT ANSWERS
Straight answers to what buyers ask first.
How is it priced?
We agree the scope, fees, and subscription terms before work begins. Bring us a workflow and we can prepare a proposal for your review.
Where does my data go?
Before deployment, we document the proposed model route, hosting, access path, data classes, and return terms for your review. The agreed boundaries go into your deployment agreement.
Can we choose the model and still choose where it runs?
Yes. Model and hosting choices are separate. We can assess public frontier models by separate agreement, private open-source or open-weight models where supported, and customer-provided routes by agreement. The exact model, data classes and host are confirmed for your deployment.
Do we have to replace our systems?
We start by assessing connections to the systems you already run. Any required changes are identified in scope.
How long does it take?
It depends on the systems involved. In the Briefing we tell you what drives the timeline for your workflow. During configuration (Phase 0 of your bolde. deployment) we agree scope, timeline and target go-live date in writing before the Build.
Do you do work without bolde.?
We only take on work we deliver on bolde.. If you need something else, we'll say so in the Briefing.
Which certifications do you hold?
The Trust Center ledger does not list a held certification. Ask for the current evidence packet during the Briefing.