1 slot open · booking from dec 2026→
$ whoami

stefan
./kovachev

senior ai engineer. i architect and build products end to end: agents, mcp, typescript, react, laravel.
// software architect · full-stack since 2010 · sofia, bg · remote
profile.ts
1
type Role = "AI Engineer" | "Architect" | "Full-Stack" | "Lead" | "Founder";
2
3
interface Profile {
4
  name: string;
5
  roles: Role[];
6
  stack: { ai: string[]; web: string[] };
7
  availability: boolean;
8
}
9
10
const me: Profile = {
11
  name: "Stefan Kovachev",
12
  roles: ["AI Engineer", "Architect", "Full-Stack"],
13
  stack: {
14
    ai: ["agents", "mcp", "rag", "evals"],
15
    web: ["typescript", "react", "php", "laravel", "mysql"],
16
  },
17
  availability: true, // 👈
18
};
$ ./services --available

01. services

I take a problem and ship the smallest thing that solves it, solo or embedded in your team for a quarter or two.

what-are-we-building.mp4

On-screen text, in order:

  1. it starts as an idea.
  2. built all the way down.
  3. and it works.
  4. ai that fits your business.
  5. agents your team can trust.
  6. products, built end to end.
  7. fixed, not rewritten.
  8. what are we building?
function aiFeatures()
  • ·Agents, retrieval and extraction on your data
  • ·Guardrails, evals and cost limits before launch
function agentWorkflows()
  • ·Rules, skills and MCP servers your agents share
  • ·Review gates, so your engineers ship more without lowering the bar
function fullStackBuild()
  • ·Greenfield from idea to production
  • ·Ops-heavy apps: workflows, admin tools, integrations
  • ·Architecture that still makes sense in year two
function rescueMission()
  • ·Diagnose before touching anything
  • ·Fix what's costing you sleep, nothing else
  • ·No big-bang rewrites
function launchSaaS()
  • ·Auth, billing, ops dashboards, monitoring
  • ·Skip the commoditised parts, I've built them before
  • ·Ready for your first paying customer
function consulting()
  • ·Architecture review with written findings
  • ·An honest assessment, including where AI doesn't fit
  • ·Implementation help if you want it
$ git log --oneline --selected

02. selected work

cronboard.io
cronboard.io logo
phplaravelvuejavascriptterraformtailwind
private beta · early customers
~/cronboard.io
2018 →
SaaS · Founder

→ Cron monitoring built solo: ingestion, alerting, billing, dashboard.

antero
antero logo
typescriptreactphplaraveljavascriptdocker
bg team 1 → 4
~/antero
2021 →
Lead Full-Stack · Tech Consultancy

→ Lead developer on a loan origination workflow system, from prototype to production.

flip
flip logo
phplaraveljavascriptfull-stack
key delivery on major client releases
~/flip
2015 →
Senior Full-Stack Developer · Web Agency

→ Built LMSs and a live-streamed event platform, and brought Laravel in as the agency's stack.

william hill
next
little chef
anywhere on wheels
owners direct
nz marine
angling trust
med creations
mdm design
40+ builds · most still running
~/bespoke-client-work
2010 →
Freelance

→ A long list of complex web apps across three continents. Mostly under NDA.

$ cat ai.md --summary

03. ai engineering

What the model does inside the product, and how agents help build it.

function aiInProduct()
  • ·Agents and model features working on your own data[4][5][6]
  • ·The model never makes a decision that costs money unchecked[4][5][6]
  • ·Structured data from messy input: web pages, chat, voice, spreadsheets[4][7]
  • ·Workflows automated from request to booked job[3][6][7]
function aiInBuild()
  • ·Specs and rules any coding agent can pick up[2][3][8]
  • ·Multi-agent workflows with defined roles and review[3][4][7]
  • ·MCP servers that give agents live docs, errors and data[2][3][4]
  • ·Rules agents can't edit, and checks before anything merges[3][5][8]
$ man stefan

04. about

Stefan Kovachev
→ portrait.jpg

❯I build bespoke web apps for ops-heavy businesses, the kind where spreadsheets stopped scaling six months ago.

Full-stack dev, obsessive about architecture: the domain model, the boundaries, and the boring infrastructure that keeps it up at 3am. I spec, design and review; agents handle the volume. Having built it all by hand is why I know when they're wrong.

Started at SAP Labs and Fraunhofer back when "ajax" was still a buzzword. Picked up a Diplom in digital media in Kaiserslautern and an MBA from Worcester somewhere along the way.

Three spoken languages, bg, en and de, plus fluent typescript.

16y
shipping web apps
11y
at flip
40+
projects shipped
$ ./engagement.sh --new

05. how i work

~/sk/engagement.sh
$ ./engagement.sh --new
[1/4]discovery(fixed fee)
We get on a call. I read your repo / docs / mess.
You get a written plan and an honest yes / no / not-yet.
[2/4]build(milestone-driven)
Working software at each milestone, demoed, with whatever questions came up.
No status meetings about status meetings.
[3/4]handover
Docs, runbook, deploy keys, the whole envelope.
[4/4]aftercare(optional · monthly)
I stick around for the bugs you find in week 5.
Cancel any time.
$ _
$ ssh stefan@kovachev

> let's build()

Something gnarly that needs untangling, or a greenfield project that needs shipping? Send a message. I reply within a day.

$ echo "© 2026 · built in sofia, shipped to the edge"
privacy