Custom software is software written for how your business actually works, instead of bending the business around a package. We design, build and run it, as a small studio in Athens.
We started from our own products. Kommo is a hiring marketplace, Forkly is a restaurant ordering platform in public preview, and Mesito is a real-estate CRM. We build client software the same way we build these.
What do we build?
| Kind of software | Typical example | More detail |
|---|---|---|
| SaaS and multi-tenant platforms | One product serving many businesses, each with its own data | SaaS platforms |
| Web apps and PWAs | A marketplace, a portal, a tool used on phones all day | Web applications |
| Internal tools | A CRM, a scheduling or back-office system for your own team | Web applications |
| APIs and integrations | Connecting your systems to payments, email, maps or partners | Included in each project |
Do you build workflow automation?
Yes. Many projects begin as a manual process: a spreadsheet, a shared inbox, a chain of phone calls. We turn that into a system with clear roles, a history of who changed what, and notifications. Our operations and workforce CRM is an example from our own work: scheduling, settlement and audited corrections in one system.
How do we build it so it lasts?
Most software problems appear in year two, not in the demo. These are the habits that avoid them.
- Data in a real database. We use PostgreSQL for business data and S3-compatible object storage for files. Nothing important lives on one server’s disk.
- Safe to run in more than one copy. Sessions, locks and scheduled jobs are stored in the database, so a second server can be added later without rewriting the code.
- Background work in queues. Emails, imports, video processing and reports run in workers, not inside the web request.
- Changes that do not break the live system. Database changes are made in stages, so the old and the new version of the app both work during a release.
- Tests, backups and monitoring from the start. Not added after the first outage.
Who runs it after launch?
We can. We host, monitor and maintain our own three products, and we offer the same for client work. If you would rather run it yourself, we write down how it is deployed, backed up and restored, so you or another team can take over. Ownership is agreed in writing before work starts.
How does a project begin?
With a short call about the goal, the users and the limits. Then we write a scope and give a fixed quote. The services overview shows the whole sequence, or you can go straight to the contact page.