Skip to content

Corporate, commercial and institutional systems

We don’t build systems.We build the way pastwhat’s stalling your company.

Corporate systems, commercial platforms and institutional websites — built around what is jamming your operation, not around a catalogue of modules.

12

years building software

40+

systems in production

60

companies served

99.9%

average uptime

What we do

Three practices, one way of working

The kind of system changes. The method does not: diagnosis before screens, scope in writing, fortnightly delivery and support with an agreed response time.

How we work

Seven stages, from diagnosis to support

None of them is optional and none of them is a surprise. You know what happens at each stage before you sign anything.

  1. Diagnosis

    We learn the operation before drawing a single screen. Who does what, where it jams, what systems already exist and what cannot stop during the switch.

  2. Scope and proposal

    What is included, what is not, and what it costs — in writing. A deadline with a date, not a vague estimate.

  3. Architecture

    Data model, integrations, infrastructure and security plan settled before the first line of code.

  4. Prototype

    A clickable interface for you to approve. Changing a flow here costs an afternoon; changing it after launch costs weeks.

  5. Development

    Fortnightly releases, with a staging environment always online. You watch the system take shape instead of receiving a sealed box at the end.

  6. Rollout

    Data migration, team training and close support through the first weeks of real use.

  7. Maintenance

    Support with an agreed response time, fixes and continuous evolution. The system stays alive after handover.

Technology

Tools chosen for the problem, not for the trend

Everything we use has a large community and available talent in the market. Your system cannot depend on a technology only we know how to maintain.

  • TypeScript
  • React
  • Node.js
  • PHP
  • Laravel
  • Vue
  • PostgreSQL
  • MySQL
  • Redis
  • SQLite
  • Docker
  • Nginx
  • Linux
  • AWS
  • React Native
  • Flutter
  • PWA

People we have worked with

In the words of the people who signed

  • prov
    They were the first supplier who asked how we work before showing us a screen. The system came out looking like the operation, not the other way round.
    Ana RibeiroOperations director
  • prov
    Shipping every fortnight changes the relationship. We corrected course along the way instead of discovering the problem at go-live.
    Marcelo TavaresIT manager
  • prov
    I asked in the first meeting who owns the code. They said "you do", and put it in the contract. I had been burned before by a supplier sitting on the repository.
    Juliana PradoManaging partner
  • prov
    Month-end close was the week nobody wanted. It now takes a morning, and the team looks at margin instead of reconciling spreadsheets.
    Rodrigo AmaralController
  • prov
    Our connection drops constantly and the till used to stop with it. They treated that as a requirement, not an edge case — the shop sells offline and syncs on its own.
    Patrícia NunesRetail coordinator
  • prov
    What convinced me was a dated deadline in the proposal instead of "four to eight weeks". They slipped once and told us beforehand, which is already more than I was used to.
    Eduardo BastosSales director

Next step

Describe the problem. We answer with scope and a deadline.

Half an hour is usually enough to tell whether this makes sense. If it does not, we say so — it is cheaper for both sides.

Rather talk now

Message on WhatsApp

We use these details only to answer you. No mailing lists. Privacy policy