About
Get the integration live. Then make the process repeatable.
Bailey Wildash Ltd is a small UK consultancy for API, payments and data integrations, and for the Claude Code skills that make that work repeatable.
What it is
A small, specialist practice
I'm Chris Bailey. Bailey Wildash is my consultancy. I get complex integrations live and then make the process repeatable. Most of the work sits between a signed deal and a working integration: checking what was promised, owning the dependencies, reviewing the architecture where money or data moves, and proving behaviour with tests rather than assuming it.
The second half is agentic. I write the same process down as Claude Code skills and workflows that live in your repo, so an agent can prepare the call, check the docs and draft the plan, and a person can check its work without redoing it.
It is deliberately small. You get senior attention on the actual problem rather than a team assembled around a statement of work, and a straight answer when something is outside what I can do well.
Built the same way
This site is maintained by an agent skill
A Claude Code skill keeps the copy on these pages up to date. It drafts changes from my notes on methods and tooling, and writes them in general terms.
Allowlisted notes
Hashed per file
Changed files only
Unchanged files are skipped
General wording
Drafted in general terms
Guard
Blocks company names, people, personal data, keys, dashes and phrases copied from the notes
Blocked: publish stops
Blocked: publish stops
Diff shown
I read the changes
I say yes
Nothing deploys until I approve and push
How I work
Operating principles
The working rules that decide whether an engagement was worth paying for.
Label every claim
Documented, observed or inferred. An inference never gets promoted to fact because it sounds right.
Do not bluff
If I do not know the answer, I say what I do know, what needs checking and the fastest way to check it.
Turn repeats into tooling
When a problem turns up a second time, I document it, script it or take it to the product team. Handling it by hand every time costs more.
Write it where it lasts
Decisions, blockers and owners go in files the team keeps, not in meeting notes nobody reopens.
Leave it runnable
Skills, checklists and test harnesses stay in your repo and keep working after the engagement ends.
Say when it is not worth doing
Including when the honest answer is that you do not need me for this one.
Fit
Who I work with
- API and developer platforms
- Payments and fintech
- Digital asset infrastructure
- Solutions and post-sales teams
- Teams adopting Claude Code
- Startups selling into enterprise
Size matters less than the shape of the problem. A twelve-person developer platform and a large business rolling out a complicated integration often have the same blockage.
Boundaries
What I do not do
- Take work outside what I can do well
- Publish client names or case studies without permission
- Sell headcount, or resell somebody else's
- Recommend a rebuild when a fix will do
- Tell anyone a product makes them compliant. Regulatory interpretation goes to your legal or compliance owner
Client work appears here only with permission. Nothing invented in the meantime.
Expertise
Technical ground covered
The depth behind the services. I start from the problem, not a favourite tool. The one fixed choice is Claude Code for the agent work.
Integration architecture
How the pieces fit, and where they break under retries and partial failure.
- APIs
- Webhooks
- Idempotency
- State machines
- Auth patterns
- Serverless
- Web and mobile SDKs
Testing & evidence
Proving behaviour rather than assuming it.
- Sandbox harnesses
- Contract checks
- Docs diffing
- Endpoint grading
- Reconciliation
- Observability
Delivery & commercial
The work between the customer conversation and the codebase.
- Technical discovery
- Sales handoffs
- Implementation plans
- Go-live readiness
- Incident triage
- Adoption reviews
- Product gap cases
Payments & digital assets
Infrastructure for products that move money or touch a chain.
- Pay-ins
- Payouts
- Fiat onramps
- Wallet flows
- Settlement states
- On-chain data
- Travel Rule data flows
Agentic tooling
Encoding a team's process so an agent can run it and a person can check it.
- Claude Code
- Skills
- Subagents
- MCP
- Retrieval with provenance
- Evaluation
- Human sign-off
Most engagements draw on more than one of these. The interesting problems usually sit where two of them meet.
Have a technically difficult problem?
Say what the system is, what is stuck and when it needs to be live. One short call usually settles whether bringing me in is worth it.