Software development to simplify your work
I build customer portals, booking systems, and document and invoicing solutions. I connect them to your existing software.
- Custom business software
- Integrations with Estonian services
- You own the code and infrastructure
Software to solve recurring problems
Work often starts with one obstacle: orders are tracked in Excel, customers ask about order status, or invoices are prepared manually. I build the smallest software needed to solve it.
Customers can see their orders, invoices, documents, and status themselves. Fewer emails and phone calls, less manual responding.
A booking system for your website: available times, confirmations, reminders, and cancellations without manual calendar work.
Quotes, contracts, and invoices are generated from data, not copied from one file to another. E-invoice sending and receiving.
Bank links and card payments, Smart-ID, parcel lockers, accounting, email, and CRM—the systems talk to each other.
A single view of orders, stock, sales, or projects. Numbers come from the system, not a manually maintained spreadsheet.
An assistant based on documents, request pre-processing, or drafts. AI where it saves measurable time.
Connecting systems
I connect the services you use when they have a suitable interface. If integration is not possible, I will say so before work begins.
- Smart-ID and Mobile-ID: secure sign-in and signing without building a separate password system.
- E-invoicing and accounting: sending and receiving invoices; connection to Merit Aktiva, Directo, or e-Financials if their APIs allow it.
- Payments: bank links, card payments, and order status through a payment service.
- Logistics: parcel-locker selection and sending shipment details (Omniva, DPD, and others) when the service has an interface.
- Everyday work: Microsoft 365, Google Workspace, email, WooCommerce, and CRM—data goes where work already happens.
- Public registries: company and property data, environmental data, and other open sources when they have an API or regular data feed.
Important: an integration is more than “connect to the API.” It includes error handling, retries, logging, and what happens when the other system does not respond. That is what separates a working solution from a demo project.
How the work proceeds
Assessment
I review the work with you and explain what needs to be built, what does not, and how I will measure the result.
Small working version
I build the first usable part. I show you a working version regularly so you can try the result.
Launch and handover
I configure the solution in your account, document it, and hand over access. We agree on maintenance separately.
Why take a small step instead of a large project
Large software projects most often fail because the first usable version arrives too late. After half a year, no one remembers why a particular requirement was written down, and the first feedback comes when changing the architecture is already expensive.
- Weekly demo: you see progress and can change direction before it gets expensive.
- Fixed scope: each stage's price and outcome are written down before starting.
- No vendor lock-in: standard technologies, your repository, and your infrastructure.
- Documentation: the start-up guide and architecture decisions are documented.
Price and handover
- Assessment · €0One conversation and a written scope with the price of the first stage.
- First version · 2–3 weeksA usable part, not an endless specification.
- Code · yoursRepository and infrastructure in your account.
- Maintenance · separateMonitoring, fixes, and further development based on volume.
Frequently asked questions
Is it worth building custom software or buying an off-the-shelf solution?
If the process is standard—accounting, project management, or email—an off-the-shelf solution is almost always more sensible. Custom software is worthwhile when the workflow sets the business apart, off-the-shelf solutions do not integrate, or adapting them would cost more than a small build.
Which integrations can you build?
Examples include Smart-ID and Mobile-ID authentication, e-invoicing, bank links and card payments, parcel lockers, accounting software (Merit Aktiva, Directo, e-Financials), Microsoft 365, WooCommerce, and public registries—if a service has an API or standard, it can be connected.
How long does custom software take to build?
A small usable version is usually ready in 2–3 weeks when the scope is defined. A larger system is divided into stages; each stage ends with a working part that can be used in practice.
Who owns the code and infrastructure?
Your company does. The code is in your repository, the infrastructure in your cloud account, and the documentation is written down. I do not use vendor lock-in or hide access.
See also: B2B SaaS development, AI development and integrations, AI automation, and AI assistant and knowledge base.
Describe the obstacle. I will find a suitable solution.
I will talk with you about your work and explain whether a small piece of software, a system integration, or a simpler solution would fit.