Factumsoft
About us

Factum means fact

We named the studio after the thing we kept asking for in every meeting: not a strong opinion, but a measurement. Nine years later that is still how we decide what to build.

What we believe

Four principles we actually apply

Not wall art. These are the arguments we have internally, settled in advance.

01

Evidence over opinion

Factum means fact. We prefer a measurement to a strong feeling, and we will show you the benchmark rather than describe it.

02

Small teams, senior people

Every engagement is staffed with engineers who have shipped and then maintained what they shipped. No layers between you and the build.

03

Boring where it counts

We take risks on product ideas, never on databases. Proven infrastructure keeps the interesting parts of the work interesting.

04

Honest scope

If a feature is not worth building, we will say so before you pay for it. Trimming the plan is part of the service.

Projects delivered
180+Projects delivered
Partners worldwide
70+Partners worldwide
Years building
9Years building
Engineering support
24/7Engineering support
Our story

From three engineers to four time zones

We grew slowly and on purpose. Every year on this list is a year we could staff properly.

Work with us
  1. 2017

    Founded by three engineers who were tired of shipping software they would not want to maintain.

  2. 2019

    First enterprise platform delivered; the team grows to twelve and opens a second studio.

  3. 2022

    Dedicated AI practice formed after a year of production retrieval work for logistics clients.

  4. 2024

    Cloud and reliability practice launched, bringing deployment and observability fully in house.

  5. 2026

    Forty engineers across four time zones, still working in squads of four.

How we staff

Squads of four, senior throughout

A Factumsoft squad is deliberately small: enough people to cover product, interface, build and infrastructure, few enough that everyone holds the whole picture in their head.

  • A tech lead who writes code on your project every week
  • A product designer working in the same repository
  • Two engineers splitting product and platform work
  • Shared on-call for anything already in production

“We would rather hand back a smaller system that your team can own than a larger one that only we understand.”

Saribek SaribekyanCo-founder & Principal Engineer

Want to see how we would approach your build?

Send us the problem, not a spec. We will come back with how we would scope it — and tell you if we are the wrong fit.

Get in touchView pricing