PCI hosted
PCI operates the agreed runtime and infrastructure. Your data, credentials, permissions, provider accounts and usage limits remain client-specific.
How it works
Start smaller. Connect more later.
We start with the business question, not the AI tool. The aim is one useful improvement with clear evidence, ownership and boundaries.
- 01
Free Commercial Systems Assessment
Understand the business before recommending technology. Describe how things work, what matters and a recent example. Real collection remains closed until the operating and public release controls are verified.
- 02
Human review
Josh reviews strengths, problems, evidence, unknowns and possible first steps, then prepares a manually reviewed PDF. A new implementation is not the default answer.
- 03
Scope the first improvement
Agree the outcome, boundaries, required sources, integrations, ownership and acceptance criteria. Confirm the scope and price before implementation.
- 04
Build + test
Connect only what is needed. Test outputs, permissions, review points and failure handling before relying on the workflow.
- 05
Use + learn + expand
Review whether the first improvement is useful. Keep the accepted foundation and add more only where it earns its place.
Low-friction onboarding
PCI does the preparation.
You confirm what matters.
- 01Assessment
- 02Prefilled scope
- 03Confirm
- 04Connect required tools
- 05First useful result
- 06Review
Use what we already know. Ask only for the access and decisions needed by the agreed system. You should not need to learn the technical stack or complete a long technical questionnaire.
Deployment models
Choose where it runs.
Keep responsibilities clear.
Client hosted
PCI installs or configures the agreed system in infrastructure and provider accounts you own. Access, support and handover responsibilities are agreed.
Third-party model/API usage, software, data services and hosting may be paid directly by the client. These are separate from PCI implementation and maintenance where applicable. There is no unlimited AI/API allowance implied.
Secure connections
Your accounts.
Only the access required.
Create the required provider account or dedicated project, add your billing, then approve a secure connection with minimum necessary permissions.
Where a project credential is needed, connect it through the agreed secure method. Never send passwords or API keys by email.
Access, usage limits and responsibility for each account are agreed during onboarding.
Commercial terms
Scope first.
Agree the price before the build.
Free assessment
Human-reviewed and without obligation. No supplier-pricing calculation or automatic purchase decision.
Implementation
Scoped and quoted for the problem, current systems, evidence, integrations and complexity.
Care & Improvement
Optional ongoing service. Eligible maintenance and improvements are agreed; substantial new scope is separate.
Explore ongoing careA useful place to start
Not sure what you
actually need?
Start with a free Commercial Systems Assessment. A human-reviewed view of what matters, what could help, and what can wait.
Get my free Commercial Systems Assessment
No obligation to commission a system. We may recommend improving something you already use, or doing nothing yet.