My outreach system was completely broken. Philip diagnosed the root causes immediately, rebuilt the workflow, and delivered comprehensive documentation.
I find the loop that's eating your week, and I close it.
Discovery to handover. One person, start to finish; the thing that ships matches what you actually need.
Three steps. No mystery.
Every engagement moves through the same shape. I write it out so you can hold me to it.
- 01
Discovery
Two calls and a workshop. I trace the loops, name the bottleneck, and cost the fix. You leave with a scoped plan whether we work together or not.
- Process walk-through
- Friction ledger
- Scoped plan + estimate
- 02
Design
I prototype the end-state on your data. You see the workflow, not a slide about it. We cut what looks clever and keep what earns hours.
- Working prototype
- Interface + data contracts
- Acceptance checks
- 03
Build & handover
Ship in two-week slices. Instrumented, documented, and owned by your team on day one. No black-box lock-in.
- Incremental rollout
- Runbooks + observability
- Handover + 30-day warranty
Hours returned. Errors gone. Friday back.
Two recent engagements. Numbers measured against the quarter before go-live, not against sales decks.
Strong technical expertise; sharp attention to detail. Communication was clear and consistent throughout, and every deadline was met.
Learn the automation that the rest of your org is buying.
I run a Skool community for two kinds of people: leaders who want to stop being fooled by demos, and engineers who want to ship AI workflows that survive the first bad Monday. Six weeks of structured modules, live office hours, and a room that doesn't speak in buzzwords.
- Systems thinking for non-engineers
- Picking tools without lock-in regret
- Prompting, evals, and when to stop
- Shipping a first workflow in week one
- Observability: knowing it still works Monday
- Office hours + cohort reviews
What people ask before booking.
What size engagements do you take?
Discovery is always a fit. Build engagements are scoped to the workflow; complexity and timeline determine the investment. Anything that’s better served by a template than a person, I’ll say so and point you at the course if it’s a fit.
How does pricing work?
Depends on scope. After the discovery call I send a fixed-price proposal; what I quote is what you pay. No hourly billing, no surprise add-ons.
How long until something ships?
First working slice in two weeks. Full handover in six to ten, depending on scope. I work in two-week increments so you see real movement; no waterfall that surfaces bad news in month three.
Which tools do you build on?
Whatever you already own, first. I favour n8n, Python, Postgres, and the Anthropic + OpenAI APIs, but I’ll sit inside your stack if that’s cheaper to run. No referral kickbacks, ever.
What about our data?
I sign your DPA before Discovery. Data stays in your infrastructure by default; I bring code into your environment, not the other way around. EU-hosted models (Mistral, Anthropic EU) available when GDPR posture requires it.
Course or consulting: which should I pick?
If you have a team that can build, buy the course and let them ship. If you need it live in your ops this quarter, hire me. The discovery call tells you which you are. It’s free and I’ll say so either way.
Let's see if we're a fit.
Describe the loop. I'll review and reach out within one business day to ask the awkward questions.
- No slidesI'll ask about your week. Specifics, not positioning.
- No NDAs up frontWe talk scope freely. Paperwork follows only if we both want to work together.
- No obligationIf the course is the right answer, I'll tell you. If nothing is, I'll say that too.
Rather write directly? freelance.pprentki@gmail.com