AK

A Koppelmaa OÜ 16534175

--:--Tallinn

Services

Consulting, programming, and the stretch between them.

A Koppelmaa OÜ works where a technical decision and the software that follows it belong in one place. You can hire the thinking, the building, or both.

01 — IT consulting

A written view before the budget gets nervous.

Consulting is for the moment when a team can feel the problem and cannot yet name the system. We study what is already in place, who depends on it, and which constraints are real. The result is a recommendation you can revisit in six months without having to remember the meeting.

It is also the right shape when a vendor proposal, a rewrite, or a new product idea needs a second reading from someone who will not be paid to inflate it.

  • A written account of the problem, the constraints, and the options.
  • Architecture for a new system, or a simpler shape for an old one.
  • A first slice small enough to teach you something before the rest is funded.
  • Review of a design, a codebase, or a proposal you are about to accept.
  • Help deciding what should stay unbuilt for now.

02 — Programming

Software designed to be operated by people who were not in the room.

Programming at A Koppelmaa is the design and construction of working software: the interface a person actually uses, the rules underneath, and the joins to the other systems you already pay for. We favour tools a careful team can keep running, and we say why a choice was made.

The usual materials are web applications, internal tools, APIs, and changes to an existing codebase. A spreadsheet that has become the business, a queue of emails that should have been a workflow, a service that needs a clean integration — these are familiar shapes.

  • Web applications with real work behind the screen, not a brochure with a login.
  • Internal tools that replace a fragile chain of files and inboxes.
  • APIs and integrations between systems you already rely on.
  • Automations for operational work that should not need a person each time.
  • Changes to a codebase you have, made so the next reader can follow them.

03 — Continuity

After the release, the system still has to live somewhere.

Launch is a poor ending if the only person who can deploy, explain, or extend the work is the one who just finished the invoice. Continuity is the handover, and the option to stay near afterwards under a named arrangement.

Where we can, the repository and the hosting accounts are yours from the first week of a build. Access should not be a souvenir we keep.

  • A walkthrough with the people who will own the system next.
  • Notes on how to run, change, and recover the software.
  • A retainer for fixes, small features, and advice after the first release.
  • Source and credentials arranged so a future supplier can take the work up.

04 How it is bought

Three shapes. The agreement names which one you are in.

We do not publish a rate card. Price follows the shape of the problem, and the honest way to price a build is often a short discovery first. What follows is how the work is usually held.

Discovery

A bounded piece of thinking.

A short engagement that ends in a written recommendation. Useful when the path is unclear, and a complete product in itself when what you needed was the decision.

Build

A project with a named outcome.

Design and programming against a scope we both can point at. The scope can change. The change is named before the work drifts.

Retainer

Time held open across a month.

For a product or a system that keeps moving. Advice and implementation, still written down, without opening a new contract for every small slice.

05 Where to start

Three questions. A sensible first engagement, not a quote.

Answer in your own words later. This only chooses a starting shape you can send through the contact page.

Step 1 of 3

What do you need most right now?

A strong fit

  • A product or internal system that needs judgment and programming together.
  • A team that wants decisions written down, and software it can own.
  • Work that can be shaped in stages, with room to stop or redirect.
  • English or Estonian, with the client anywhere we can meet remotely.

A different partner

  • A round-the-clock operations desk or a staffed support line.
  • A large programme that needs many coordinated teams.
  • A certified audit, a penetration test, or a compliance attestation.
  • Body-shopping: unnamed developers supplied by the week with no responsibility for the result.

06 Questions

Practical answers, before the first call.

If yours is missing, the contact page is the shorter route.

Yes. The company is Estonian and established in the EU, and almost all client work is remote. We correspond in English and Estonian. Contracts and invoices use the registered details on the company page.

A Koppelmaa OÜ is owned and represented by Alari Koppelmaa, the member of the management board. You deal with the person responsible for the company. When a piece of work needs another specialist, that is named in the agreement rather than hidden inside a team slide.

Yes, for a defined piece of advice or programming alongside your people. We are a poor fit when what you need is anonymous extra capacity with no ownership of an outcome.

The agreement names it. Our starting point is that software we are paid to build for you is yours, along with the repository and the notes required to run it. Third-party libraries stay under their own licences, which we keep visible.

Invoices are issued by email from A Koppelmaa OÜ, VAT number EE102803930. The company is not set up to receive e-invoices. Share your company VAT number if you have one, so the invoice can be prepared correctly. This is bookkeeping, not tax advice — your accountant should confirm the treatment on your side.

It follows the shape of the problem. Send a rough sense of the outcome, what already exists, and any date that matters. We will tell you whether we are a fit, and whether the next step is a discovery note or a proposal for a build.