01
The same data gets typed twice
Once in the message, once in the spreadsheet, sometimes a third time in the invoice. The three do not always agree, and nobody knows which one is right.
Internal apps and automation
Starts with a two-day audit
The process works. It works because someone remembers it.
The thing your company runs on lives in a chat group and a spreadsheet. I turn it into one place with a history, roles and a report, so it stops depending on who is in the office.
From 3,500 EUR, after a two-day audit at 600
You usually get here after one of these
03Three signs the spreadsheet has run out of road.
02
Nobody knows the state without asking
What happened with that order, who took it, has it been paid. The answer exists, in someone's head or in a chat from Tuesday afternoon.
03
One person is the system
They know which file is the current one and what the colours mean. When they are away the company slows down. When they leave, it stops.
What I build, by name
Four things, and none of them a dashboard.
01
One record everyone looks at
One place where the order, the job or the client lives, with its history. Not two versions of the truth and not a file called final_v3.
02
Roles, so each person sees their own work
What the office sees, what the person in the field sees, what the owner sees. Different, and decided once instead of every time someone new arrives.
03
Forms that refuse what is wrong
A date that cannot be in the past, a quantity that cannot exceed what is in stock, a field that cannot be left empty. Errors stop at the door instead of being found at the end of the month.
04
The report that does not need assembling
What came in, what went out, who did what, exportable. There on the first of the month without anyone staying late to build it.
A smaller piece, on its own
One flow, with the hours counted.
1,200 EUR and up
If a whole app is more than you need, there is a narrower piece. Data pulled out of documents or emails and put where it belongs, or requests that arrive and sort themselves instead of waiting for someone to read them.
It is sold against a measurement rather than a promise: how many items a month, how many minutes each one takes now, and what is left afterwards. You see the saving as a number before you order it, and you can check it afterwards.
It gets things wrong sometimes, so there is a step where a person looks before anything counts as done. A supplier who tells you otherwise is selling you the version that fails quietly.
Before, and after
Five places that do not agree.
Where the state of one order lives now
A chat groupA spreadsheetSomebody's inboxA paper noteSomebody's memory
Where it lives after
One record
With who changed it, and when.
How it gets built
With AI, and internal is the right place for it.
I decide what gets built and in what order. The implementation is written with AI. I test it, and I am the one who answers for it.
Internal is where that trade is clearly the right one. A mistake inside a company of eight people shows up the same day and gets fixed. No money leaves for a stranger, no customer sees a half-finished state, and nothing is public while it settles.
It is also why I sell this and not an AI assistant sitting on your customer data. That one is asked for constantly, fails quietly, and cannot be guaranteed by anybody, including me.
The proof
What I can show, and what I cannot.
Internal apps delivered so far: none
I have not yet delivered an internal app for a company. I put that here rather than let you find it out in the second meeting.
What I have delivered is the same machinery pointed at customers instead of staff: accounts, roles, payments and access that opens and expires on its own, at jemshitmavlyanov.com and elenaviscu.com. A record with a history, roles and a report is less demanding than that, not more.
That is exactly why the entry is a two-day audit and not a contract. You pay for two days, you get a document, and you decide with it in your hand.
You get a document with:
- The map of the process as it runs now, not as the procedure says it runs
- What can be automated, and what the time saving is in hours a month
- What stays manual, and why it should stay manual
- What gets built first, what second, and what it costs
If we go further, the 600 EUR comes off the price of the work.
If we do not, you keep the document. It is yours, and you can hand it to anyone else.
The three ways in
Smallest first, and each one stands alone.
- Process audit
- 600 EUR
- Two days
- Deducted from the project
- One automated flow
- from 1,200 EUR
- One to two weeks
- Sold against a measurement
- Internal app
- from 3,500 EUR
- About four weeks
- Estimated after the audit
Write me what the process is and who is holding it together, and I will tell you whether it is worth two days.
Write to me
Answered the same working day, in writing. Sometimes the answer is that a spreadsheet is still the right tool, and you get that answer too.