Service

Automation, APIs & Payments

Copy-pasting data between three systems by hand ends here.

Custom APIs and middleware integrations between systems, internal dashboards for project management and reporting, fast low-code/no-code builds when a full custom system isn't needed yet, and billing integrations (Stripe, Chargebee, local banks) with automatic invoicing into Merit Aktiva, Standard Books or Erply.

  • Custom API with OpenAPI documentation
  • Cross-system integration (CRM, accounting, warehouse)
  • Internal dashboard built around a specific workflow
  • Automated report generation and delivery
  • Low-code prototype for fast validation (Retool, Make)
  • Stripe/Chargebee integration for recurring billing
  • Automatic invoicing into your accounting software
  • Failed-payment recovery (dunning) logic
  • Multi-currency and tax-form support

Examples

Typical situations and how I'd handle them

Metal fabrication company (real case)

A production plan that updates itself

Problem

The planners' Excel list was slow, showed already-planned parts and lost rows.

Solution

Data straight from the ERP, filtered correctly and refreshed every two minutes, with a warning when data goes stale.

Result

~20× faster processing and a list you can trust. See it under Selected work.

Wholesaler

Orders from email straight into the system

Problem

Customers email their orders and someone retypes them by hand.

Solution

Automation reads orders from email, checks the product codes and creates the order in the system: anything suspicious goes to a human.

Result

Orders are in the system within minutes, not the next day.

What's included

What I do as part of this service

CRM ↔ accounting ↔ warehouse, one integration

Data moves between systems automatically, no one has to copy it by hand.

An internal dashboard as a prototype in a week

Project management, time tracking or reporting in one view, built around your actual workflow.

An API that's documented and tested

OpenAPI spec and automated tests so integrations don't fail silently.

A quick fix on Retool/Make/Zapier when time is tight

A working tool in days, not months, when full custom development isn't (yet) the right call.

Automated reporting straight to your inbox

Weekly or monthly reports generate and send themselves: no manual spreadsheet assembly.

Recurring and usage-based billing

Stripe or Chargebee configured around your pricing model: monthly, annual or usage-based.

Invoices land in accounting automatically

Merit Aktiva, Standard Books or Erply get invoice data straight from your store, no manual entry.

Failed-payment recovery logic

Automated reminders and retries reduce subscription churn.

Multi-currency and tax-form support

International customers handled without separate manual bookkeeping.

  • Node.js
  • REST/GraphQL
  • Retool
  • Make
  • Supabase
  • Stripe
  • Chargebee
  • Merit Aktiva
  • Erply

FAQ

Frequently asked questions

Do you start with low-code or straight to custom code?

Depends how time-critical it is. For fast validation I start with a Retool or Make prototype. If the process is already clear and stable, I build the proper solution straight away.

Can you connect old systems?

Usually yes. If a system has an API, database access or even just a file export, I'll find a way to connect it.

What does an internal dashboard typically cost?

A simple single-view dashboard starts in the low thousands of euros; a more complex multi-source tool is scoped per project once we’ve discussed volume.

Do you support local Estonian banks?

Yes, alongside Stripe I integrate local bank payments as well, when the business model calls for it.

Which accounting systems do you integrate with?

Mainly Merit Aktiva, Standard Books and Erply: for other systems I assess API availability case by case.

Can we switch pricing models later (e.g. monthly to usage-based)?

Yes, the architecture is built flexibly so a pricing change doesn’t require rebuilding the system.

All frequently asked questions

Get started

Still copying data by hand?

Name the systems you move data between. I'll tell you how much of it can run on its own.