Business automationIntegrationsCustom software
I'm Dzmitry, a software engineer. I automate repetitive office work, connect apps that don't share data, and fix the old Excel, VBA and .NET software your business still runs on.
If this sounds like your week, you're in the right place.
Every Friday, another spreadsheet needs fixing.
Related service: Excel & reportingYour team is the integration between two apps.
Related service: IntegrationsThat report takes longer to prepare than to read.
Related service: Reports & dataOne old application runs the business. Nobody wants to touch it.
Related service: Legacy softwareThe same numbers are typed into three different places.
Related service: Workflow automationNobody trusts the totals, so someone checks them by eye.
Related service: Data checksRecognize one? Tell me how it works today. That's enough to start.Describe your problem
I learn how the process works first, then make the smallest change that fixes it for good.
Repetitive steps, done by software.
If a task follows the same steps every time, a small program can run it on a schedule, even at 3 a.m.
Keep Excel. Lose the busywork.
Excel is often the right tool. It's the manual steps around it that hurt.
Numbers you don't have to double-check.
Recurring reports, imports and reconciliations with the checks built in, so nobody has to squint at the screen.
Systems that talk to each other.
If people retype data from one app into another, the apps should be doing it instead.
Software that fits how you work.
Sometimes the answer is a small, focused app, or a real database behind the spreadsheet everyone is afraid to sort.
Repair first. Replace only when it's worth it.
An old application that runs the business needs careful repair, not a panicked rewrite.
Most of my client work is under NDA, so names and figures stay private. This is the kind of work I do.
Document processing · client under NDA
You don't need a specification to start, and the initial assessment is free. Nothing begins until you've agreed to it in writing.
Through the form, in your own words: what happens today and what bothers you about it.
By email or on a call. If needed, I look at the files or the process itself.
What I'll change, what's out of scope, and the estimated cost and timeline.
You check each step on real examples, so there are no surprises at the end.
Working, documented and explained to the people who use it. If you want support afterwards, it goes into the agreement.
I work on the software businesses depend on: Excel files full of macros, desktop apps, SQL Server databases and the connections between them. Often it has been running far longer than anyone planned.
BoringJob is just me. I read every message myself, and if we work together, I do the work.
I also build and publish my own iPhone apps: NapKit, FeedKit, KartGarage. They're my own products, not client work.
More about meWhat people usually ask first. More on the contact page.
No. Tell me what happens today and what you'd like to change. Working out the technical side is my job. If a written spec would help, we'll write it together.
Yes. One macro that keeps breaking, one report, one integration. If something is too small to be worth a project, I'll say so.
From the scope we agree on. The initial assessment is free, and you get the estimate in writing before any work starts.
There are no prices on this site because a two-hour macro fix and a system migration have little in common.
A fair question for a one-person business. I document the work so another developer can pick it up. What gets handed over, and when, is part of the proposal.
I use it only to reply and to discuss a possible project. It isn't used for marketing or sold. The form sends your message to me by email, and the privacy notice lists the services involved and how long messages are kept.
If you need an NDA, we can sign one before you share anything sensitive. Please keep confidential data out of your first message. A general description is enough.
A few sentences is enough. I'll read it myself and reply by email.
Describe your problem