• Applications & Products · Next.js

An internal system: when the work lives in twenty spreadsheets and one person's head

First there was one spreadsheet. Then a second, for a different task. Then the agreements moved into chat threads and the deadlines into a manager's memory. This works longer than you would think, and it always breaks the same way: somebody goes on holiday, and it turns out half the knowledge went with them. An internal system is not about being fashionable. It is about the company's work living in one place and not depending on who happens to be at work today.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Focus
custom systems on Next.js and PostgreSQL
after a free audit
Price
30
Guarantee

days after project sign-off

custom systems on Next.js and PostgreSQL
Focus
30
Timeline

to 120 working days

free review of the processes
Start
30
Warranty

days from the date the acceptance act is signed

within 2 hours
Reply
under a written contract
Terms
What's included

Complete list of work and what you get as a result

  • a first working circuit for one process that can actually be used, rather than the whole system at once
  • documents born from data: the details are corrected in one place, not in every file
  • access rights: who sees what, who changes what, who only reads
  • a change history — who did what and when, with no more «who edited this»
  • background jobs instead of reminders in someone's head: deadlines, overdue items, regular reports
  • migrating what has accumulated in the spreadsheets, verified on the spot
  • working from a phone where that is genuinely needed, rather than everywhere
  • a written description of how to add new things when the process changes
When this service isn't right

What's not included — so there are no surprises at delivery

  • an off-the-shelf system at the price of custom development: if a ready solution fits, we will say so
  • replacing your processes with our ideas of the right ones
  • accounting and tax bookkeeping — that is the business of specialised programs
  • a guarantee that all staff will move into the system straight away
  • promises of saving a specific number of hours
Who it's for

Situations where this service delivers results

Scenario 1 of 4

A company that has outgrown spreadsheets

There are more than ten files, each with its own version, and nobody is sure which one is current. The classic moment when a system is already needed.

We'll review your situation in a free audit
Free review of the processes

We look at how the work goes now and whether a custom system is genuinely needed: often a ready solution is enough.

What we measure

  • What hurts mostThat is where we start. A system built «all at once» does not launch for years; a system for one painful process works within a month.
  • Whether a ready solution existsWe check honestly. If your process is standard, an off-the-shelf CRM will cost several times less, and saying so is our duty rather than a loss.
  • How many people will use itTwo or twenty are different requirements for access rights, change history and how far the system has to be protected against mistakes.
  • Which documents come outThe fastest return is usually here: documents from data remove manual work and mistakes in the details at the same time.
  • What about the existing dataSpreadsheets kept for years are almost always inconsistent. Migration is separate work, and its scope has to be assessed in advance.
  • Who will actually use itThe main risk is not technical. A system the staff bypass is money spent, and it is better to talk about that before the start.

What you get

  • a description of how the work goes now, in your own words
  • an answer on whether a ready solution would do instead of a custom one
  • a proposal on which process to start with and why that one
  • an estimate of the first circuit broken down by stage

Timeline: 3–7 working days

Why is it free

The most important decision — build your own or take a ready one — is made before any code. Selling development where an off-the-shelf product is enough is easy, but afterwards both of us have to live with it.

What's next

You get a description of the processes and an estimate. Then you decide for yourself — the document stays with you.

Short form: your contact and site URL

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • European clients

    Among our work — projects for Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of processesThe main driver. One circuit is months. Deals, documents, projects, stock and reporting together are years, and they have to be built in a queue.
  • Complexity of the rulesSimple data storage is cheap. Multi-step approval, conditional discounts, document versions — every rule has to be described and checked.
  • Documents as outputA template with value substitution is straightforward. Conditional blocks with automatic renumbering and versions is a task of a different scale.
  • Exchange with other systemsEvery exchange is separate work: accounting, the bank, messengers, electronic document flow. And each breaks independently of the others.
  • State of the existing dataSpreadsheets kept by several people over years have to be tidied before migration. Often that is the longest stage.
  • Number of rolesOne user with full rights is simple. Five roles with different access to different fields is a separate layer that has to be tested.
Cases

Tasks and results in numbers — all metrics measured by us

the agency's own CRM: deals, contracts, invoices, acceptance acts, projects and a client portal

Task
Stop running the agency in chat threads and spreadsheets: bring deals, versioned contracts with approval, invoices and acts, projects, licences for our own products and client communication in messengers into one system — and make documents be born from data rather than typed in by hand.
Solution
An application on Next.js 16 with Supabase (authentication and RLS) and Prisma. A contract builder with templates, versions, comments and conditional option blocks; signing a contract automatically produces the invoices and the act. Document exchange with Vchasno, National Bank rates with daily snapshots for converting EUR into hryvnia on the invoice date, bank receipts, fiscalisation through Checkbox. Client communication in Telegram and Viber with a single history. A separate circuit for our own products: licences, deployments, domains, support tickets. 35 background jobs cover the routine: reminders about invoices and meetings, digests, lead scoring, health monitoring of integrations and backups, synchronisation with Vchasno.
Result
As of 02.08.2026 the system runs in production (first server response 188 ms — the fastest response among all the projects we have measured). 121 dashboard pages across 38 sections, 489 server routes, 20 tables in the data schema, 11 enumerations and 27 classifier types, 35 scheduled background jobs. 958 commits over 10 months of continuous work. Data exchange is set up with roughly two dozen external systems.

Did not find your case?

Describe how it works on your side — we will tell you whether “An internal system for a company” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:30–120 days

  1. Reviewing the processes

    3–7 working days

    We write down how the work goes now, together with the exceptions — it is exactly those that break ready solutions. This decides whether a custom system is needed.

  2. Choosing the first circuit

    1–3 working days

    We pick one process to start with. The criterion is simple: most pain and the fastest visible return. The rest waits its turn.

  3. Data and roles

    5–15 working days

    We design what the system stores and who sees what. A mistake here costs the most: reworking the data store later is painful.

  4. The first circuit

    15–50 working days

    We bring the process to a working state, with documents and a change history. The goal is that it can be used, not demonstrated on a screen.

  5. Migration and launch

    5–20 working days

    We move what has accumulated in the spreadsheets, check it on real data and launch with your people. We stay close for the first week.

  6. The next circuits

    by separate agreement

    After that the system grows by processes rather than in one big push. Each next one rests on a foundation that has already been proven.

Technologies & integrations

What we build on and what it connects to

Stack

  • Next.js
  • React
  • TypeScript
  • Node.js
  • PostgreSQL
  • Prisma
  • Supabase
  • Docker
  • Tailwind CSS
  • Git
  • GitHub
  • Linux

Integrations

  • 1C
  • BAS
  • Telegram
  • Viber
  • Email
  • National Bank exchange rates
  • Checkbox
  • Vchasno
A custom system or a ready solution

How this option differs from the alternative

Fit to the processa system built around your way of working
Time to first benefitmonths
Costnoticeably higher upfront
Future changesany you like, it is your code
When ready is betteroverkill for a standard process
What we need from you

We can't start without this — best to prepare in advance

  1. a description of how the work goes now, with every exception to the rules
  2. who will work in the system and what each of them does
  3. which documents are needed as output and in what form
  4. what hurts most — that is where we start
  5. which systems are already in use and whether data has to be exchanged with them
  6. who on your side accepts the work

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

Would it not be simpler to take a ready CRM?

Very often — yes, and we will say so outright during the review. A ready solution delivers benefit in weeks and costs several times less. A custom system is justified where your process is genuinely non-standard and breaking it to suit a program costs more than writing a program to suit it. If that is not your case, taking on development would be dishonest.

Why not build it all at once?

Because systems built «all at once» most often never launch. A year and a half of work with not a single day of use — and in that time the processes manage to change. We start with one painful process, bring it to a working state, and only then take the next.

How much does it cost?

There is no price list, and any figure before the review would be invention. The difference between a first circuit for one process and a system across five areas is several times over. What can be said in advance: it costs more than an off-the-shelf solution, which is exactly why we check first whether an off-the-shelf one would suit you.

And if the staff do not want to work in it?

That is the main risk, and it is not technical. A system that gets bypassed is money spent. So we ask about it during the review and start with the process where the benefit is felt by the people doing the work, not only by the manager. But we cannot and will not guarantee other people's behaviour.

What happens to the data in the spreadsheets?

We migrate it, and that is a separate stage with its own estimate. Spreadsheets kept by several people over years are almost always inconsistent: different spellings, duplicates, empty fields. Some of it has to be tidied by hand — yours, because only you know what is correct.

Do you do accounting?

No. Accounting and tax bookkeeping are the business of specialised programs, which do it better than any custom development. We can exchange data with them, but we do not take on replacing them.

How long does it take?

30 to 120 working days for the first circuit. After that the system grows by processes rather than in one push. The timeline is set not by programming but by how much time you can give to reviewing the processes and checking the result — without your involvement it does not happen.

Whose code is it and what happens if we part ways?

The code is yours, and that is written into the contract. We deliberately do not build systems that tie the client to the contractor: we use ordinary common technologies rather than our own closed solutions, and hand over the access together with the work.

Let us work out whether you need a custom system

We will describe your processes and say honestly whether a ready solution would do. The review is free, we reply within 2 hours.

From measured casesAs of 02.08.2026 the system runs in production (first server response 188 ms

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.