Work · Full rebuild · B2B accounting SaaS (under NDA)

A B2B accounting platform, rebuilt in three weeks.

An accounting product with paying customers ran on FastAPI, React, a BPMN workflow engine and six Docker services. Three developers maintained it. 1703 Group rebuilt it on Phoenix LiveView and reached feature parity in three weeks.

-63%

code: 68,850 lines became 25,185

6 → 1

Docker services to run and monitor

218 → 78

dependencies, from three ecosystems to one

3 → 1

engineers needed to maintain it

The problem

  • The product ingests documents, extracts data with OCR and LLM services, and gives multi-tenant reports. The stack had grown to four languages.
  • A Java workflow engine, its monitoring UI, Elasticsearch and Redis existed mostly to support each other.
  • Five environment files, two test runners and two package managers made every change slow and every audit long.

What we built

  • Week 1: we mapped the database schema and the domain model, then got file upload, document processing and the basic accounting views to work on Phoenix 1.8.
  • Weeks 2 and 3: we ported the workflows to Oban background jobs, rebuilt the React frontend as LiveView, and rewired the LLM and OCR integrations.
  • The data moved from MySQL to PostgreSQL.

What went away

  • The workflow engine and its monitoring UI, Elasticsearch, Redis, gRPC and the separate REST API.
  • The React application: 398 component files became 3 templates and 3 JavaScript files.
  • Infrastructure configuration went from 5,448 lines to 439.

Result

  • One language, one service, one configuration file. A new developer can read the whole codebase in a day.
  • The scope of compliance audits fell by about half, because there are fewer services and data flows to map.

Stack

  • Elixir
  • Phoenix 1.8
  • LiveView
  • Oban
  • PostgreSQL

Have a system that needs the same treatment?

Tell us what you run today. In 30 minutes we tell you honestly whether a rebuild pays off, and what it takes. See how a rebuild works →

Book a 30-min call