DEVEXANA CONSULTING Amadeo Bonde

Claude Certified Architect · Anthropic

AI engineered for maximum
uptime on every run.

I build the automations and AI systems that still run after I leave. Describe what you need the way you'd tell a friend. I handle everything from there. Private material can stay on your own machines. You own all of it.

Book a call

Scroll to drop in

race_bib

01BIB

RACER · AMADEO BONDE

CERTIFIED ARCHITECT

CLAUDE PARTNER

CREDLY · ANTHROPICALL LIFTS · ALL SEASON

Gate 1 · Services

Three runs down the same mountain.

Pick the one that matches where you are right now. They all end the same way. You get the codebase, the accounts, and a plain-English manual. It's all yours, and the thing runs without me.

green_circle.txt

Individuals · easiest way down

You keep doing it by hand. Let's make it automatic.

A morning text with the three numbers you check anyway. A weekly report that writes itself overnight. One form fill that quietly kicks off the next five steps. Small automations that keep running after you stop thinking about them.

Engagement: One build, start to finish. You never need to learn how it works.
Typical duration: Days, not quarters.
What you leave with: The finished automation, running on your accounts, with a manual anyone can follow.

blue_square.txt

Businesses · more pitch, more consequence

Systems that hold after the handoff.

Agents and automations your team can actually run without me. A record of what happened and who asked for it. Rules about who is allowed to set what in motion. An undo for the day it goes sideways. It lives on your systems, under your accounts. There's no platform of mine you keep renting.

Engagement: Scoped build, then a real handoff to your people.
Typical duration: Weeks, shipped in stages you review.
What you leave with: A system your team runs day to day, with the records and controls to back it up.

black_diamond.txt

Prototype → production · steepest

The demo works. Now it has to survive real users.

It works on your machine, when nothing goes wrong, while you're watching it. I take it the rest of the way. What happens when it breaks, when too many people use it at once, when the answer comes back wrong, and how you'd even know. All the unglamorous work that decides whether it's still running in six months.

Engagement: I make what you built strong enough for real customers.
Typical duration: Depends how far the demo got. We scope it on the call.
What you leave with: Your product, ready for real customers, and built to stay standing.

Gate 2 · Recent runs

A few things I've shipped.

What each one actually does, first. If you want the technical detail, ask me on the call. If you don't, you'll never need it.

podcastbrief.exe

Yesterday's podcasts. This morning's brief.

Overnight it listens to the shows I follow, writes them down, checks the claims against the original sources, fills in what's thin, and drops a PDF in my inbox before coffee. If I want to dig into a line, I text the brief and it answers from the same material.

Listens overnightSource-checkedPDF + text

offline-brief.exe

Point it at a YouTube playlist. Wake up to a brief.

Same idea, no internet. The listening, the summarizing, and the writing all happen on the computer sitting in front of you. Nothing gets sent to an outside company, because no outside company is involved.

OfflineRuns on your machineOvernight job

devexana.exe

Founder of Devexana — an AI system that runs inside town and county IT departments, on hardware they own.

It looks, it doesn't touch. Every action goes into a permanent record nobody can quietly edit, and anything that would change a piece of equipment stops and waits for a person to approve it. It runs on a machine in the building, not in someone else's cloud.

On-sitePermanent recordA person approves

viralreels.exe

A trend goes in. A finished vertical video comes out.

It picks up the trend, writes the script, voices it, cuts it, captions it, then stops. A person approves before anything posts. That's the one step you don't hand to a machine.

Scripted + voicedAuto-captionedYou hit publish

Gate 3 · The toolkit

What I've actually put my hands on.

No certification wall. Just an honest count of what the year actually looked like.

toolkit.log

1 yrDaily
Claude Code

71Projects
built

46Tools built for
AI to use

local → cloudOn your machine, or
the cloud, your call

Anthropic certifies me as a Claude Certified Architect – Foundations. Their wording for what that covers is designing and building production-grade applications with Claude using Claude Code, the Claude Agent SDK, the Claude API, and MCP. In plain terms, those are the four ways to build on Claude, and I'm signed off on all four. So you get the one your problem actually needs, not the one I happen to know.

I also hold the Anthropic Claude Partner badge for Claude Code. That credential's own scope is to scope, deploy, configure, and run Claude Code activations end-to-end. In plain terms, that means one person handles all of it. I come in at the first conversation and I'm still there when it's live in front of real users.

Gate 4 · Questions

The things people ask before they book.

Answered the way I'd answer them on the phone.

faq.exe

I'm not technical. Can you still help?

That's most of the people I work with, and it's my favorite kind of project. You never need to learn what any of it means. You describe the thing you keep doing by hand and roughly what "done" looks like, and I handle everything from there. You leave with the codebase, the accounts, and a plain-English manual, so nothing depends on me picking up the phone.

What does it cost?

We scope it on the call and you get a fixed quote in writing before any work starts. Nothing begins until you say yes to that number, and no meter runs while you think about it. If the honest answer is "this isn't worth building," I'll say that instead of quoting it.

Who owns what you build?

You do. The code, the accounts, the data, all of it. Nothing is held hostage. There's no platform of mine you keep paying for to keep your own system running.

Does my data get sent off to an AI company?

Only if you decide it should. My default is to run the AI on hardware you control, so the sensitive material never leaves your building. When an outside service is genuinely the better call, I'll tell you which one, exactly what it would see, and what it costs. You make that call with the facts in front of you.

What if I just have an idea?

Bring the idea. Half these calls start with someone describing an annoying Tuesday. Part of my job is telling you whether that's a weekend build, a real project, or something you're better off not building at all.

How long does it take?

Depends on the run. A personal automation is usually days. A system your team operates is usually weeks, shipped in stages so you're looking at working pieces the whole way instead of waiting on one big reveal.

What happens after you hand it off?

You get a manual written in plain English for whoever has to fix it at 8am. What it does, where it runs, what tends to break, how to start it up again. If you want me around after that, we talk about it. It isn't a subscription you get enrolled in.

Can you work with my team and the tools we already use?

Yes, and that's most of the interesting work. Anything already running has real constraints, real users, and real history behind it. I'd rather fit into what you already use than talk you into replacing it.

What if it doesn't work?

Then we find out early, on purpose. I build in stages so the first checkpoint is small and cheap to walk away from. Learning something is a bad idea in week one is a good outcome. Learning it in month six is what I'm here to prevent.

Will you sign an NDA?

Happily. Send yours over before the call and we can go straight into specifics.

Finish · The lodge

Base of the mountain. Let's talk.

Thirty minutes. Tell me what you keep doing by hand, or what already broke. Nothing to prepare and no jargon required. You'll leave the call knowing whether I'm the right person for the job, and I'll tell you straight if I'm not.

scoreboard

YOUR RUN--:--.--

You made it to the bottom. That's the pitch. Book the debrief and we'll talk about your run instead of mine.

book_a_call.exe

The booking calendar didn't load. No problem, this link goes to the same place.

Open the calendar