Skip to content
PrismaCoders
Talk

The same bill every month: what you pay to redo it by hand.

Before comparing the price of a system, compare it with what already leaves the bank every month to keep a process running by hand. This page does that sum — and also says when off-the-shelf software is the right answer.

Do that sum with us
  • The cost of a manual process appears on no invoice
  • A subscription is rent; custom software is in your company name
  • If off-the-shelf solves your case, we say so on the call

The sum nobody does.

The cost of a manual process is spread across hours of people you already pay, which is why it shows up nowhere. Add these three together and compare them with the price of a project.

  1. 1

    Hours of typing and checking

    Someone copies data from one system into another, checks a spreadsheet and fixes what came through wrong — every week, at the same effort as last week.

  2. 2

    The report rebuilt from scratch

    Month-end, commissions, stock, indicators. The same manual assembly every month, and the number only exists once somebody assembles it.

  3. 3

    The rework when an error slips through

    An order typed wrong, a duplicate invoice, a customer complaining. Here the cost is not only the hour spent fixing it.

Multiply by twelve. That is the number a project has to beat — not the price of a subscription.

Rent it or own it.

Off-the-shelf software solves the problem everybody has, which is why it costs little. When the process is precisely what makes your company different, it starts forcing you to work like everybody else.

Off-the-shelf

A subscription per user, forever. You adapt to what exists, and whatever is missing becomes a spreadsheet running alongside the system.

Custom

Invested once, then evolved as the business changes. The code and the repositories are in your company name.

When off-the-shelf wins.

Many of the companies that come to us do not need custom software. If you recognise yourself in this column, we say so on the call instead of selling you a project.

Stay off-the-shelf if

  • The process is common to your sector and is not what sets the company apart.
  • A shelf product covers almost everything you need.
  • You need to be using it next week.
  • The budget cannot carry a project right now — and half a system is worse than a spreadsheet.

Building is worth it if

  • The process is your advantage, and off-the-shelf forces you to do it differently.
  • Two or three tools already exist, with somebody in the middle copying data by hand.
  • Growth runs into the capacity of a single person.
  • The data exists, but is never ready at the moment of the decision.

Four stages, no black box.

You approve scope, architecture, timeline and cost before the first line of code. After that, partial deliveries and demos the whole way through.

  1. 1

    Understand

    A conversation about process, bottleneck and business priority — not about stack.

  2. 2

    Design

    A proposal with scope, architecture, timeline and cost. Nothing starts without your approval.

  3. 3

    Build

    Partial deliveries and frequent demos — you see it before it is finished.

  4. 4

    Sustain

    Support, maintenance and evolution as the business changes.

Work we have shipped.

A few systems now running in production, described with each client’s permission.

Velani Digital

Accounting / fintech

Velani Digital

Accounting needs turned into software, from requirement to production.

Challenge
The online accounting platform needed accounting and business needs turned into software: financial reports, tax documents and billing, with requirements gathered directly from the client.
What we built
Requirements gathering with the client, then the screens and flows themselves, Angular on the front end and Laravel on the back, plus the REST APIs and external integrations the accounting workflows run on.
Result
Demands delivered end to end, inside the platform roadmap and deadlines, alongside maintenance and fixes to features already in use.
  • Angular
  • TypeScript
  • Laravel
  • MySQL
  • REST APIs
Hort-e

AgTech / marketplace

Hort-e

Family farmers selling straight to the people who buy.

Challenge
Family farmers had no direct sales channel of their own: between the person growing the food and the person buying it there was always a middleman.
What we built
A cross-platform Flutter application for iOS and Android with a PHP backend and REST APIs: product catalogue, producer listings and the order flow, with authentication and secure communication between app and server.
Result
An iOS and Android application delivered in a three-month project, with catalogue, producers and ordering working end to end.
  • Flutter
  • Dart
  • PHP
  • MySQL
  • REST APIs
AO4

Digital agency / platform

AO4 — Tribo da Sorte Online

Back end and front end of an online lottery-pool platform.

Challenge
The agency had to deliver its client a complete lottery-pool platform, covering business rules, user accounts and purchasing, within an agreed scope and deadline.
What we built
A PHP backend with REST APIs covering pools, participants and results, and a responsive Angular front end for browsing, joining and managing pools, with authentication and secure communication for accounts and purchases.
Result
The platform delivered within the scope and deadline agreed with the agency, across a six-month project.
  • PHP
  • Angular
  • TypeScript
  • MySQL
  • REST APIs

Do that sum with us, with no obligation.

Tell us how the process works today. If off-the-shelf solves it, we say so. If it does not, you get a proposal with scope, timeline and cost.

Describe my process