For solo professionals and small businesses who want to keep up with bigger players while staying nimble.
Years building custom software. Co-founded Gatera Studio (interactive software, VR/AR for enterprise clients). Now using AI to run my own practice across five projects, and walking you through it below.
For solo professionals and small businesses who want to keep up with bigger players while staying nimble.
Years building custom software. Co-founded Gatera Studio. Now using AI to run my own practice across five projects, and walking you through it below.
Live demo · Real Claude · Real context
Live demo below. Real Claude. Real context, loaded before the conversation starts.
See it in action ↓Most professionals who try AI hit the same wall. The output is generic. They re-explain. They re-paste. Drafts still need heavy editing. So they shrug and go back to typing things by hand.
The conclusion looks like "AI isn't ready". The reality is that the AI doesn't have what it would need to be useful. Your clients, your decisions, your voice, your active projects, all live in your head and across half a dozen tools that don't talk to each other. The model can't see any of it.
That's a software problem before it's an AI problem. A programmer would solve it for you whether AI existed or not. The fact that AI exists is what makes the payoff much bigger: once your work is structured, the same model that gave you generic answers suddenly knows your business.
Pick any prompt below. Claude has access to the same context I built for my own practice: five active projects, hundreds of decisions, every email thread. The response is real, written in this conversation, not pre-recorded.
That's not a trick. The system that produced this answer is the same kind of system I'd build for you. Different data, same architecture.
Plain text files on your machine. Clients, decisions, project notes, drafts. The layer that makes everything else work. Without it, the AI is guessing. With it, it has access to the same picture you do.
Your principles and workflow shape in plain text. Claude reads it on every call. Grows into topic-scoped rule files as your work does: email-voice.md, proposal-structure.md, meeting-prep.md.
Reusable workflows in plain markdown, triggered by a "Use when X" line. Example: draft-email-reply pulls thread context, drafts in your voice, flags open questions.
The tools Claude acts through. Gmail, Calendar, Drive, Notion, Slack, almost every tool you use has one. A few picked around your day.
From €500. Most setups pay for themselves in the first month.
You walk me through a normal week. Ask me anything about AI. I tell you where the setup would save you the most hours, and whether this fits your work at all. No pitch, no obligation.
I study your workflow, then send you a document: the setup I'd build for you, what's included, what's not, and a budget. You decide from there.
We build it together, live. Your structure, your CLAUDE.md, your skills, your connectors. 60 to 90 minutes, depending on how deep we go. By the end we're using it on real work: an email you owe, a proposal you're drafting, a decision you're about to make.
Everything lives in plain text on your machine. I hand you a short guide for extending the setup yourself: adding rules as your work evolves, codifying new skills, wiring new connectors when you need them.
From €500. Most setups pay for themselves in the first month.
You walk me through a normal week. Ask me anything about AI. I tell you where the setup would save you the most hours, and whether this fits your work at all. No pitch, no obligation.
I study your workflow, then send you a document: the setup I'd build for you, what's included, what's not, and a budget. You decide from there.
We build it together, live. 60 to 90 minutes, depending on how deep we go. By the end we're using it on real work: an email you owe, a proposal you're drafting, a decision you're about to make.
Everything lives in plain text on your machine. I hand you a short guide for extending the setup yourself: adding rules as your work evolves, codifying new skills, wiring new connectors when you need them.
30 minutes. I respond within 24 hours. No prep required. Pay only if we go ahead.
I'm Pol Ferrando, a software engineer based in Barcelona.
I've been writing code for over a decade, mostly on the interactive end of software. The kind of work where engineering and design have to agree. I co-founded Gatera Studio, where we built interactive software, VR/AR for enterprise clients, and games. I've always cared as much about how things look as how they work.
Now I run my own practice the way I'd help you run yours. Five active projects. AI that already knows the clients, the decisions, the deadlines, the voice. I spent the last year figuring out what to keep and what to throw away. The setup is me handing you only the parts that matter.
You'd work with me directly. There's no junior consultant doing the work while a partner sells it. The methodology is documented (this site is itself an artifact of it), so what you're buying isn't trapped in one head.
Bringing this work to clients beyond my own practice now. No client testimonials yet.
Three sketches of what the first engagements look like, with names and details abstracted.
Was pasting old briefs into ChatGPT to get drafts of new proposals. The AI didn't know the clients, the rates, or the deliverables. After the setup: a Claude with the past five projects loaded as context, and a one-prompt "draft a proposal" skill. Three hours back per week.
Was reading every prior brief by hand to find precedents. After the setup: a structured set of decision notes, plus a Claude that retrieves the precedents with the original reasoning attached. Reading goes from 90 minutes to 10.
Had to context-switch between client books constantly. After the setup: a per-client CLAUDE.md, a connector wired into their books and inbox. Status check on any client in seconds, in the same voice.
Real case studies will replace these as the first paid engagements ship.
Your data stays on your computer. The Claude API doesn't retain it for training under Anthropic's standard terms. Anything we wire (email, calendar, drive, your tools) uses your existing accounts and your existing permissions. No data goes through me.
You can. ChatGPT knows nothing about your clients, your past decisions, your writing voice, or your workflow. Context engineering is the difference between asking a generic AI a generic question and asking your AI a specific question about your work. The tool isn't the value. The configuration is.
It works best for solo professionals and small teams whose work product is mostly text: proposals, briefs, decisions, communications, client emails. It's a weaker fit for visual-tool-dominant work (CAD, video editing, design files). If you're not sure, the free call answers it.
You don't have to. The same way you don't have to understand a database to use a CRM. The free call answers in language you'll understand, and an honest read on whether you should DIY this.
You could. I already did the year of figuring out what to keep. The setup hands you only the parts that matter, configured to your work, in one session.
The structured work outlives the AI. You end up with the cleanest project history you've ever had, even if the AI side commoditizes.
You're hiring a specific person's judgment, not a firm. The person who does the work is the person you talk to. The methodology is documented (this site is part of it), so the value isn't trapped in one head.
If your work is mostly text and you've been pasting context into AI again and again, the free call answers whether the setup would save you hours. No pitch. Pay only if we go ahead.
30 minutes. I respond within 24 hours.