For advisors and fractional CTOs

Your word with the client. Our engineering behind it.

For advisors whose clients need software built, automated or kept running. You keep the relationship. We deliver, and we answer for the delivery.

Arhivix, our own product, is built and run by us and serves 500+ companies.

What stays with you. What moves to us.

With you

  • The client's trust.
  • The strategy and the priorities.
  • The decision on what gets built, and when.

With us

  • The engineering team.
  • The build, and the work of keeping it running.
  • A written report every month: what we fixed, what we changed and the hours it took.
  • Saying so when a rewrite is the better call.

Plainly: we have not yet taken over a system another vendor wrote. What we can show you is software we built and still run.

Software we built and still run.

  1. MaxPlayer 

    With our partner E Galactic e.U., we have built and maintained MaxPlayer since 2020, backend included. 1M+ people use it.

  2. BELGRAND ScoreMaster 

    For Antena Net DOO BELGRAND we built the mobile app and, later, the desktop software behind live LED scoreboards. Desktop releases go through more than 1,700 automated tests and a beta channel, with the previous version kept for rollback.

  3. Arhivix 

    Arhivix is our own document platform, used by 500+ companies. We build it and run it ourselves, from the Go services to the desktop and mobile apps. Other software connects to it through a REST API, signed webhooks and an MCP connector.

    For integrators: arhivix.com/developers

How we take on a system you already run

How it starts.

  1. Bring one client situation.

    A system that worries you, or a process that eats hours.

  2. We read before we promise.

    • One to two weeks with read-only access.
    • A map of the system and a list of its risks, worst first.
    • A plan and a fixed price for what comes next. You can stop there.
  3. We deliver, and we put it in writing.

    • Releases through a test channel, with the previous version kept for rollback.
    • A written report every month: what we fixed, what we changed and the hours it took.

Working terms, in plain sentences.

Whose name is on the work
Ours by default. If the work has to go out under your firm's name, we agree that in writing before we start.
Your client stays yours
We do not approach your client for work that did not come through you.
Who owns the code
The client owns all source code and IP outright, delivered in their own repositories. There is no lock-in and no per-seat licensing.
Who holds the keys
Code, cloud, domains and payment accounts sit under accounts the client controls.
Who answers
A Notix team does the work. Both founders answer for every system we run.
Our home stack
Go and TypeScript are our home stack, on servers, the web, phones and TV apps. If the client's system is far from that, you will hear it in the review.
If we part ways
The client keeps a system they can run without us.

What we have not done yet

  • Most of what we run, we built from the first line.
  • We have not yet taken over a system another vendor wrote.
  • We do not hold a SOC 2 or ISO 27001 certification yet.
  • We have not done technical due diligence for an investor yet.
  • If a rewrite is the better call, you will hear it in the review, not after the contract.
The full list

FAQ

Common questions.

Start with one client and one problem.

Tell us what the client runs and where it hurts. The first step is a Technical Review, as described on the ownership page: read-only access for one to two weeks, then a plan and a fixed price, and the client can stop there.