Twenty years · shipping business software · 10× · what agencies deliver, in the time they'd still be scoping · Free · first version, yours to keep · Chicago, USA · working worldwide

Custom software. Ten times faster.

I don't sell systems. I ask what your business actually does, then build exactly the software it needs — with AI multiplying what a solo engineer can ship. Twenty years of experience, delivered in days, not months. Your first version is free, so you can see the work before you commit a dollar.

You're trying to make an ERP fit, and it almost does.

Most businesses I talk to have already tried two or three things. Maybe it was Odoo, or NetSuite, or SAP Business One, or Zoho, or QuickBooks stretched well past what it was meant to do. Some of it works. Some of it almost works. And there's this one part — the part that really runs your operation — where every system falls short in the same frustrating way.

Usually it's not that the software is bad. It's that your business doesn't fit the template, and the customization path looks painful: the vendor wants $80,000 and six months, or a consultant quotes you something impossible to verify, or the plugin you need was written in 2018 and hasn't been updated since.

So the gap lives in spreadsheets. In macros. In a tool somebody built on a weekend and never touched again. In tribal knowledge that lives in one person's head. It works, mostly. Until it doesn't.

Call me if any of this sounds like you:
  • Your ERP covers most of the business but the part that makes you money lives somewhere else entirely
  • You're paying per user or per module for features your team will never use
  • Some ancient system is still running a critical piece of your operation and nobody wants to touch it
  • Excel macros and spreadsheets are doing the job that real software should be doing
  • A consulting firm promised a digital transformation, you spent the money, and nothing changed
  • You've outgrown QuickBooks and stitched it together with Airtable and eight Zapier connections

Your first version is on me.

A thirty-minute call

We talk about how your business actually runs — not the slide-deck version, the real one. What breaks. What takes too long. Who does the weird workarounds.

A free working first version

One to two weeks of my time. Real software, running on a staging environment your team can touch. Not a prototype, not a mockup — the actual first slice of what you'd use every day.

You decide from there

If it works for you, we scope phase two and keep shipping — weekly demos, fixed prices, honest pace. If it's not a fit, you keep the software I built, we shake hands, and we part as friends.

No contract. No commitment.

Not a sales tactic with fine print. The first build is genuinely free — up to about forty hours of my work on a well-defined problem. That's how I prove it's worth hiring me without asking you to trust me first.

The project is fully yours — and you can change it yourself

When we're done, I hand over everything: code, documentation, access. Then I train your team on how to modify it using AI — the same tools I use daily. Most small changes that used to require calling a developer, your people can now handle in minutes. You're not locked into me.

Where I make my money

The free first version isn't charity — it's how I find long-term clients. Real revenue comes from the months and years after, when we're shipping features, integrating new systems, and keeping your software aligned with the business as it grows. But you choose to come back, every time. It's never a trap.

What usually happens, step by step.

01
free · this week

A thirty-minute call

My part
I ask what your operation actually does. What hurts. What the quick-wins are. Which thing, if fixed first, would matter most.
Your part
Tell me the truth about how things work today. Complaints welcome. This is the cheapest moment to be honest about the mess.
Deliverable
Shared understanding of what we're solving — and a decision on whether I'm the right person for the job.
02
free · one or two weeks

I build your first version

My part
I pick the most painful piece and build working software around it. Real code, deployed to a staging environment, using AI in the loop so one engineer can ship what an agency would take a month to specify.
Your part
Give me access to the relevant systems. Be available for quick questions. Don't disappear for a week — momentum matters here.
Deliverable
Working first version on your staging environment. Not a demo — real software your team can actually use.
03
one week

You try it. You decide.

My part
I'm on call for questions. I take notes on what's missing, what's wrong, what I got right. No pressure to continue — genuinely.
Your part
Use the software. Break it. Show it to the team. Decide honestly whether you want to keep building with me.
Deliverable
A yes or a no. Both are fine. If no, you keep the code and we part as friends.
04
a few days

We scope phase two together

My part
I write a plain-language scope for phase two — what I'd build next, in what order, for what price. Fixed price, in writing, before any new code gets written.
Your part
Read the scope. Push back on anything that feels off. Sign when it reads right.
Deliverable
A fixed-price scope document for phase two — the thing that replaces the last frustrating piece of your current setup.
05
ongoing

Weekly shipping, as long as you want

My part
Working software every week. New features going into staging continuously. Every phase has its own written scope and fixed price — no surprise invoices, no scope creep.
Your part
A thirty-minute weekly review. Use what lands each week. Tell me what to build next — the priority is yours, not mine.
Deliverable
A system that does more every week than the week before — and a clean exit option whenever you want one.

A short note on the tools, for those who care.

Tools vary with the project — I pick what fits your situation, your team, and what you already have. Nothing exotic, nothing chosen for fashion. Everything you can hire someone else to maintain if you ever need to.

What I build with
PHP · Node.js · Python · TypeScript
Boring, proven languages with deep labor markets. Your next engineer will know these.
Where your data lives
PostgreSQL · MySQL · SQLite
PostgreSQL unless there's a specific reason otherwise. Your data stays on your servers.
Platforms I customize
Odoo · Zoho · HubSpot · Salesforce · Airtable
When you already have one of these and need it to do one more thing, I add the one thing.
Where it runs
Docker · Linux · AWS · self-hosted
Your servers, your choice. I'll explain the tradeoffs in plain language, then build for whatever you pick.

Who I'm the right person for — and who I'm not.

Call me if:

  • You have a specific workflow in mind and you can't find software that does it
  • You've been burned by a big agency or a long RFP process and want to work with one person directly
  • You can make the decision yourself, or you can get the person who can on a call quickly
  • You want to own the code and the knowledge — no vendor lock-in
  • You're tired of the 'six-month waterfall and cross your fingers' way of building software
  • You want to see working software in the first week, not in quarter three

Don't call me if:

  • You need a fifty-person team, 24/7 on-call, and enterprise compliance theater
  • You're shopping the cheapest freelancer — that's not what I am, and pretending to be doesn't help either of us
  • You want to specify every detail upfront and pay only when it's "done" — real software isn't built that way
  • You want the free first version but have no intention of continuing — please be honest about that, my time's finite
  • Your project is 3D games, casino software, adult content, or adversarial scraping

One client, seven years, still running.

DistilleryProductionComplianceMulti-phase
Problem
A distillery in Chicago had grown past spreadsheets. They'd tried two off-the-shelf ERPs — both could handle ordinary inventory, neither could handle their specific combination of compliance reporting and batch-level production tracking. They were tired of fighting the software instead of running their business.
Approach
We started with the warehouse — it was the most painful and the easiest to verify. Weeks later it was running. Then production tracking. Then compliance. Then orders. Each phase paid for itself before the next began. Instead of a twelve-month waterfall that might fail, it was a sequence of small bets that worked.
Outcome
Seven years of continuous delivery. The system still runs the operation today — and the code is clean enough that another engineer could take it over tomorrow if it ever made sense to hand off.

Dmytro Klymentiev

Independent engineer building custom software with AI as a force multiplier. Twenty years of the unglamorous work that makes businesses actually run.

I've been writing production software since 2004. Back-office tools, ERPs, integrations, internal web and mobile apps, data pipelines. The systems your team touches every Monday morning — that kind of work.

What changed in the last two years is AI. Used the right way, it lets a solo engineer ship at the pace of an agency — and then some. I use it daily in my work: for code, for business analysis, for documentation, for the thinking-through that used to take whole afternoons. That's why days now do what months used to.

Based in Chicago. Working worldwide — US, EU, and Asia timezones. Direct contracts, or through a US entity, or via Upwork — whichever suits your legal setup.

Questions you might have.

Wait — the first version is actually free?

Yes. Up to about forty hours of my work, on one well-defined problem. Not a sales tactic — it's how I prove the quality without asking you to trust me first. If we continue, we do it on paid phases. If we don't, you keep what I built and we part as friends.

What if I just want the free version and then walk?

You're welcome to. That's the point of the offer. I'd rather have you leave with something useful than waste both our time on a bad fit. Just be honest about it — my time is finite and I'd rather spend it with people who are actually considering continuing.

Ten times faster? Isn't that just marketing?

Honest answer: in my own work, yes. AI used well — for code, analysis, documentation, the thinking-through — has genuinely changed the math of what a solo engineer can ship in a day. Whether it lands at exactly ten times faster for your specific project, I won't know until we scope it. But agencies quoting six months for what I do in three weeks is now normal, not a surprise.

What will this cost?

Depends on what we're building — every engagement is scoped individually. The honest way to find out: we have a thirty-minute call, I build your first version free, and if we continue, I write you a scope document with a fixed price before any paid work starts. You know what you're paying before you commit to anything. No surprise invoices, no hourly billing.

Can my team maintain the system without you?

Yes — that's a core part of what I deliver. When the project wraps, I train the people who'll actually use it on how to make small changes themselves, using AI the same way I do. Adding a field, adjusting a report, tweaking a workflow — things that used to require a developer call can now be done in minutes by whoever runs that process. You're not dependent on me. You come back if you want to, not because you have to.

Can you work with our existing ERP instead of replacing it?

Honestly, this is often the better answer. A lot of my work is customization — building the one module Odoo or NetSuite or SAP can't, or wiring together the stack you already have. Full replacement is a last resort, not a first.

What if you get hit by a bus?

Fair concern, and the honest answer is — you have a contract, a scope in writing, a code repository you own from day one, documentation in plain language, and a deployment that runs on your infrastructure. If anything happened to me tomorrow, you'd still have the system and a clear way forward. That's structural, not a promise.

Will you sign an NDA?

Yes. Standard mutual NDA before we discuss anything sensitive.

Do you work with clients outside the US?

Yes. I'm based in Chicago and work across US, EU, and Asian timezones. Clients on three continents so far. Contracts can be direct, through a US entity, or via a platform like Upwork — whichever suits your legal setup best.

How fast can you start?

First call this week. Free first version typically starts within one to two weeks, depending on current bookings. If something is truly urgent, ask — sometimes there's slack.

What's not in scope?

Things I don't do: 3D games, casino and gambling platforms, adult content, adversarial web scraping, and SEO spam tooling. Everything else — most real business software — is on the table.

Written commitments, not marketing promises.

01

First version genuinely free

No hidden catch, no fine print, no automatic billing after the first version. You see the work, you decide.

02

Fixed price before any paid code

Every paid phase has a scope and a price agreed in writing. You know what you're paying. No hourly surprises.

03

Working software every week

You see progress continuously — not a big reveal at the end. Every week, something new is in staging for your team to try.

04

Your code, your servers, your keys

From day one, everything I build is yours. Your repository. Your hosting. Your credentials. No SaaS dependency on me.

05

A clean handoff, always possible

Every engagement is documented well enough that another engineer could take it over. No tribal knowledge, no magic, no lock-in.

06

Your team can modify it with AI

I train the people who'll actually use the system on how to make changes using AI — the same way I do. Small tweaks, new fields, tweaked reports — they won't need to call me back for any of it.

07

Straight answers, even the unwelcome ones

If your idea is a bad idea, I'll say so. If something is harder than it looks, I'll say so. If it's simpler — same. You're hiring judgment, not just hands.

Let's start with a free first version.

Book a thirty-minute call this week. Tell me what your business actually does — the real version, not the slide deck. I'll tell you honestly whether I'm the right fit. If I am, we skip the six-month sales cycle and I start building.

Last updated: 2026-04-23 · by Dmytro Klymentiev