Frequently asked questions
Why don't you have public case studies yet?
Because we'd rather have zero public case studies than fabricated ones. Our engagements to date are early and mostly under NDA. See Proof for exactly how programs run today, and check back — real, named case studies will appear there as engagements complete their reference periods.
The offering
What exactly does BePaza deliver, versus Depaza? +
Depaza is the underlying AI platform. BePaza is the implementation partner — we configure it, train your team on it, and stay accountable for the program's outcome. You engage BePaza; Depaza is the engine underneath.
Do we need to buy Depaza separately? +
No — access to the platform is part of a BePaza engagement. You don't need a separate procurement process for it.
Can this integrate with our existing systems? +
Yes, this is scoped per engagement during discovery. Tell us about your stack and we'll tell you plainly what's straightforward and what needs custom work.
Engagement & pricing
How is a program priced? +
Outcome-based, not a generic rate card. We scope the program with you, then propose a price tied to what you're actually trying to achieve.
How long does a typical program take? +
A pilot is usually weeks. A full enterprise rollout typically reaches meaningful scale within a few months — see Methodology for the phase-by-phase breakdown.
Can we start small? +
Yes — the Pilot Program on our Services page exists specifically to prove the approach on one real workflow before any larger commitment.
Compliance & data
Where is our data actually stored and processed? +
100% within the EU, on the Depaza platform. No US cloud fallback at any point.
Can we see the DPA before signing anything commercial? +
Yes — it's published and available on request with no obligation. See Trust & Security to request it.
How does this map to AI Act requirements? +
Risk classification, transparency documentation, and human-oversight controls are part of the standard program, not an add-on.
Delivery & team
Who actually does the work — BePaza staff, agents, or partners? +
Depends on the engagement. Some clients run the agent teams themselves after Academy training; others have BePaza's delivery team run it end to end; the largest programs often blend both — see Methodology.
What do "Emma," "Bob," "Max," and "Anna" actually do? +
They're the named roles in our agent-team model: Emma plans, Bob builds, Max reviews architecture, Anna tests. A council of models cross-checks the output, and a human always signs off before anything ships.
What happens when the agents get something wrong? +
That's exactly what the human-oversight gate exists for — nothing reaches your team without a named person reviewing it first.
Partners & getting started
How do we become a delivery partner? +
Visit the Partners page and use the inquiry form — it's the same form as general contact, with a partner option.
What happens after we submit the contact form? +
A member of the BePaza team reaches out, typically within two business days, to scope a conversation.
Do you sign NDAs before scoping calls? +
Yes, this is standard for regulated-sector conversations — just ask when you reach out.