Support
Support for the systems we've built together
Launching a system isn't the end of the work. Forms stop delivering, integrations change, content needs updating, and someone has to keep an eye on security and performance.
I offer ongoing support to clients I've already built with, as a monthly subscription. I do the work myself, with my own AI agents carrying out the execution, and I bring fixes for problems before they land on your desk.
I make the decisions. My AI agents do the execution.
Most studios pitch a senior and hand the work to juniors. I have no juniors to hand it to. I run my own AI agent workflows: the AI agents carry out the execution, and I decide, coordinate them, and check every result before it reaches you.
My part: judgment and decisions
- What to build, and what to leave out
- How it should work, and why
- Reviewing every change before it ships
- Talking with you and your team
The AI agent part: execution
- Writing and testing the code
- Checking every page after a change
- Drafting migrations, docs, and runbooks
- Watching logs, uptime, and dependencies
The speed comes from the AI agents. The quality comes from two decades of learning what good looks like.
Why a subscription, not hours or projects
An hourly freelancer starts from zero every time you call. A project ends at launch, and the context leaves with the team. A subscription keeps both from one month to the next.
This subscription
- Yes: Knows your system and its history
- Yes: Context carried month to month
- Yes: Acts before you ask
- Yes: Senior on every task
- Yes: Strategy included
- Yes: Predictable monthly cost
Hourly freelancer
- No: Knows your system and its history
- No: Context carried month to month
- No: Acts before you ask
- Yes: Senior on every task
- No: Strategy included
- No: Predictable monthly cost
Project-based agency
- Yes: Knows your system and its history
- No: Context carried month to month
- No: Acts before you ask
- No: Senior on every task
- No: Strategy included
- Yes: Predictable monthly cost
9 yearswith my longest client
Most of my client relationships run for years. Clients stay because I go the extra mile for the highest quality output, with no frills and no stress. My longest client stayed with me for nine years, and I helped with the M&A during their exit.
“It has been a true pleasure working with Mircea for over nine years as the external CTO at firma.de. Throughout this time, he was responsible for our entire IT landscape and infrastructure, while also leading the development of our founder dashboard. No matter the challenge, he was always available, approachable, and ready to help. Working with him was not only highly productive but genuinely enjoyable.”
One plan. Everything included.
A fixed monthly fee, no limit on requests, and the strategic side included. Pause it when things are quiet, stop it when you don't need it. The only thing you choose is how we communicate.
Support subscription
Everything goes through me, executed with the help of my AI agent workflows. Nothing gets handed to someone else.
- Unlimited requestsSend everything that comes up. There's no ticket count and no hour budget to watch.
- One task at a timeEach task gets finished, checked, and shipped before the next one starts. You set the order.
- Context that carries overI know the system, the decisions behind it, and last month's work. You never explain it twice.
- ShadowingCopy me on the threads where problems come up. Each week I bring a fix for what I've read, so the same pain doesn't follow you into the next week.
- Proactive, not only on requestUpdates, security, speed, and improvements I plan ahead, on top of what you send.
- Your own client portalOne login with a username and PIN. Every task on a Kanban board, and your goals and progress on one page, always up to date.
- Everything stays yoursCode, hosting, domains, and data stay in your accounts, with or without the subscription.
- Pause or stop anytimeBilled monthly. Pause for up to two months when things are quiet. Cancel by the 15th and it ends with that month.
Choose how we communicate
Async
Send requests by email or through your client portal. I reply within 24 hours.
Live
A shared chat channel for a quicker conversation while I'm working. Email and your portal are still available.
We'll agree on the systems covered and the monthly fee in a free consultation.
Book a free consultationPartner level
Included, not an add-onThis is a premium service, so the strategic side comes with it by default. You get someone thinking about where the system should go, not only fixing what broke.
- Strategic product guidanceWhere the system should go next, tied to hours saved and revenue.
- Proactive recommendationsImprovements I spot in how the system gets used, brought to you with a proposal.
- Technical consultationA second opinion on any technical decision, even outside what we built.
- Regular strategic check-insA monthly call to review what shipped and decide what's worth doing next.
All your work on one page
Every subscription comes with a client portal of your own. You log in once and see everything: what you asked for, what I'm working on, what's next, and what shipped.
- An OKR-style overview on a single page, always up to date: the goals we agreed on, the numbers that show progress, and the work behind each.
- Every task on a Kanban board, from the first message to shipped.
- Your requests, fixes I spot in your threads, and work from the plan, side by side.
- A note on every finished task explaining what changed.
An example month
Every month, something quietly costs you money. A form stops sending, a price goes stale, a page drops out of search. Nobody notices until a customer does, and by then the orders have gone elsewhere.
With support, those leaks get caught and closed first. The rest of the month goes into changes that bring in more business. Some work you ask for, some I find in your threads, some comes from the plan.
Week 1
- Impact: Stops a lossWhere it came from: From the planA security flaw closed before it cost anythingA flaw in the CMS was made public on Monday and patched on Tuesday, before anyone could use it to take the site offline or reach customer data.Outcome: Shipped
Week 2
- Impact: Stops a lossWhere it came from: Spotted in a threadQuote requests were landing in spamSales mentioned customers chasing replies. Every unanswered request is a lost order. I traced it to the form emails, fixed the mail records, and added an alert if it happens again.Outcome: Shipped
- Impact: Stops a lossWhere it came from: Spotted in a threadPrices kept right after a supplier changeA supplier announced a new price list format. I adapted the import before the first file arrived, so no quote went out at the wrong price.Outcome: Shipped
Week 3
- Impact: Brings in moreWhere it came from: Check-inHalf the visitors were leaving the quote formReviewed the numbers with you. Most requests start on three product pages, and half the people who open the quote form give up halfway. Proposed cutting it to the fields sales uses.Outcome: Approved
- Impact: Stops a lossWhere it came from: You askedSearch traffic kept after the domain mergeMapped the old URLs to their new pages, so rankings, bookmarks, and links from other sites keep sending visitors.Outcome: Shipped
Week 4
- Impact: Brings in moreWhere it came from: From the check-inA shorter quote form for more requestsFewer fields, the rest filled in by sales later. Measuring completed requests against last month.Outcome: In progress
- Impact: Brings in moreWhere it came from: RecommendationNext month: quote requests straight into the CRMScoped and waiting for your go-ahead. Sales answers sooner, and nobody copies requests over by hand.Outcome: Proposed
An illustration of how a month runs, not a record of a specific client.
What I work on
Anything from a quick question to a new workflow. Larger requests get broken into tasks and worked through the same queue. An entirely new system or a full redesign is scoped separately.
Architecture and consulting
Decisions before code: how the pieces fit, what to build or buy, and what it costs to run.
- System design and architecture reviews
- Build, buy, or no-code decisions
- Tool and vendor selection
- Second opinions on quotes and proposals
Product and design
Flows and screens people use without training.
- Landing pages, journeys, and flow mapping
- Prototypes tested with the people who use them
- Portals, admin screens, and dashboards
- Design system components
Engineering
New features and fixes in the systems you already run.
- Content management systems
- Web apps and customer portals
- Integrations and APIs
- Checkout, payments, and subscriptions
AI and automation
Repetitive work carried by AI agents, with a person on the exceptions.
- AI agent workflows for manual hand-offs
- Reading and sorting emails and documents
- Drafted replies for someone to approve
- Replacing fragile Zapier and Make flows
Data and operations
The work that keeps everything running and the numbers trustworthy.
- Hosting, domains, DNS, and email delivery
- Security updates, backups, and access reviews
- Dashboards, reports, and data cleanup
- Monitoring and incident response
How requests work
01Send it, or bring me into the conversation
Email, your client portal, or chat on Live. You can also copy me on a relevant thread.
02We set the priority
I'll tell you where it sits and when I expect to get to it.
03I make the change
I decide the approach, my AI agents carry it out, and I check the result. One task at a time.
04We look ahead
Each month, we review what changed and decide what's worth doing next.
Keep the system working
If we've built something together and you want me to keep looking after it, let's talk through what needs support and how quickly you need responses.