Pirxey stopped fitting
the company
to the tool.
Instead of another SaaS — a custom internal operating system. Time tracking as the first module, built in ~20 working days, AI‑native from day one. The foundation for the company’s full OS.
dev, one
pair of hands
AI-native software house from Gdańsk, ~150-person team, digital products since 2018. pirxey-os is their internal operating system, deployed in production.
pirxey.com
dev, one
pair of hands
company
rollout
For years, custom software was reserved for the largest companies. Expensive, slow to deploy, risky. That’s why small and medium companies chose SaaS tools. Even if they didn’t fit perfectly, they were faster and simpler to get started.
Pirxey started asking a different question:
“Can AI actually help build real, working software today — not a prototype, not a demo, but a system that can handle a company’s daily process?”
That’s how pirxey-os was born. From day one it was about something bigger than replacing a single tool.
Custom software is no longer a luxury. Pirxey stopped fitting the company to the tool and started building a tool fitted to the company.
SaaS works fast at the start.
Then the company starts
fitting itself to the tool.
“I have to do it differently than I need to. This doesn’t work the way our company works.”
And it was never a problem of a single missing feature. Companies rarely have just one SaaS. They start with one tool, add more, glue them together with integrations, until the process no longer lives in the system — it lives in integrations, exports and spreadsheets.
Time tracking as the first module
of the company’s internal operating system.
AI has changed the economics of building software. A custom system can be delivered faster and cheaper than a few years ago. The conclusion is practical:
If a process is critical, repeatable and expensive in SaaS tools, it’s worth calculating whether it should become its own system.
Diagram — from “Clockify replacement” to company OS, one development path
Six reasons why a custom system beats the next SaaS
From fit, through AI, to the math.
- 01FitThe system works according to Pirxey's process, not the other way around.
- 02ConsolidationReplacing several SaaS tools stitched together with integrations.
- 03Ownership, no lock-inBuild vs buy: your own asset instead of recurring rent.
- 04Grows with the firmEvery new need becomes the next module, not the next SaaS.
- 05AI-agent readyVia API and MCP — not just the UI.
- 06The math worksBuild vs buy: own asset instead of recurring rent.
Software that fits the company.
SaaS tools are built for hundreds of thousands of companies at once. Pirxey is one of them — but the company adapts to the tool, not the other way around.
pirxey-os works exactly the way Pirxey works, and the lower cost is just a side effect.
to the tool
to the company
One system instead of many SaaS tools.
Companies rarely have just one problem to solve. They start with one SaaS, add more, glue them with integrations, until the result isn’t a system — it’s a side effect of decisions made separately.
pirxey-os is one platform. One data model, one permission layer, one place for every process.
Diagram — ~36–93 apps in a typical company (Okta, 2024) → one coherent system
Ownership and no vendor lock-in.
If a process is critical to the company, it’s worth asking: do we want to rent it from a vendor, or own it as a company asset?
A subscription is rent. After four years, all you’re left with is paid invoices and nothing more. A custom system after that same time is a company asset that keeps growing.
The system grows with the company.
The biggest advantage of custom software is that it grows with the company — new processes become new modules.
Every new need becomes the next module of the same system, not another SaaS.
Visualisation — every new need is the next module of the same system, not another SaaS
Open to AI agents: via API and MCP, not just through the interface.
pirxey-os exposes data through a public REST API and MCP server, meaning the system can be operated by AI agents — not just by people clicking through the interface.
- Pirxey Dashboard — 18h 10m
- Med4You — 9h 30m
- Internal — 3h 20m
- Meetings — 1h 40m
The same API and MCP work underneath, used by other agents too
The same endpoint that answers questions in Telegram can be called by an n8n workflow, a Claude agent, or a CI script.
More on this model: BR-Budget case study — a finance app where the primary user is an AI agent.
{
<span class="p">"tool"</span>: <span class="s">"pirxey_log_time"</span>,
<span class="p">"project"</span>: <span class="s">"Pirxey Dashboard"</span>,
<span class="p">"task"</span>: <span class="s">"Code review"</span>,
<span class="p">"duration_min"</span>: <span class="s">90</span>,
<span class="p">"date"</span>: <span class="s">"2025-06-20"</span>
}And the numbers add up faster
than you’d expect.
Comparing the annual SaaS cost to the one-time build cost of pirxey-os.
- Recurring cost every year
- Roadmap owned by the vendor
- Limited control over the process
- After a year: only paid invoices
- Own system, not a rental
- Own roadmap and future modules
- Full control over data and process
- After a year: an asset that keeps growing
The goal here is a company asset, and the saving is just a side effect.
This is pirxey-os
in production.
Custom design system built for Pirxey: with colors, components and light and dark mode. Below: some real screens — tracker, schedule, calendar and reports. The same system, different work contexts.
Tech stack
Pirxey stopped fitting the company to the tool and started building a tool fitted to the company. It wasn’t just a decision about software — it was a decision about who we want to be.
Delivered as a full product —
from architecture to deployment.
This wasn’t a quick prototype — it was real software handling a real process in a real company: architecture, application, API, historical data import, security, tests and production deployment. All without a software house — in one pair of hands.
- 01Discovery & architectureUnderstanding how time tracking actually works in a 150-person company.
- 02System foundationFoundation designed from day one for the full multi-module OS.
- 03Design systemCustom color system, components, light and dark mode.
- 04API & AI integrationsPublic REST API, MCP server, layer for AI agents.
- 05Security & deploymentPermissions, RLS, Sentry, tests, production environments.
pirxey-os is currently used by a handful of people in production testing. Full company rollout is planned from July 1st.
Goal: all 150 people on one system. A tool fitted to the company.
One system.
One database.
A tool fitted
to the company.
pirxey-os replaced several external tools with one platform. The company stopped fitting itself to SaaS tools — the system fits itself to the company.
And it’s a company asset — not another subscription that disappears when the contract ends.
Interested in your own system?
If you’re paying for SaaS that forces workarounds, let’s check whether a custom module would be cheaper and better fitted to your process.
Fractional CTO · designer · developer. I build systems from idea to deployment: solo, with AI as the tool.