Transport management system
Dispatch, route planning, driver mobile app and accounting integration for a fleet that had outgrown spreadsheets.
- Drivers offline half the day
- Accounting system stays
- 2023 · in daily use
Custom software for companies that outgrew their spreadsheets.
We design and build the internal systems your business runs on — logistics, procurement, operations. Small senior team, direct communication, code you own from day one.
We reply within 1 business day. No sales calls unless you ask for one.
- Repos, CI and cloud accounts are yours. We work inside them, not beside them.
- Written first. Decisions land in the tracker where you can read them later.
- Two-week cycles, invoiced in advance. You can stop at any boundary.
- You leave with everything: code, infrastructure, runbooks and a written handover.
What we do
Four practices, one team. The same people who design the system run it in production.
- Custom softwareInternal systems built around how your business actually works — not around a vendor’s idea of it.
- Systems integrationConnecting the tools you already pay for so data stops being re-typed by hand.
- IT infrastructureNetworks, servers and day-to-day operations, run by people who have done it for a decade.
- CybersecurityAudits, hardening and incident response for companies without a security team of their own.
The shape of the work
Six half-systems held together by re-typing become one system with one place to look.
Dispatch spreadsheet12 tabs · 3 owners · 1 truth
Email threadswhere decisions go to die
Vendor portalsfour logins, no export
One systemEverything typed once, everyone reading the same record.
Accounting, in syncno month-end reconciliation
Numbers leadership truststhe same figure in every report
People who stop re-typinghours back, every week
Selected work
Tender discovery platform
Continuous ingestion from dozens of public sources, normalized into one searchable, rankable dataset.
- Every source formats differently
- Sources change without notice
- 2024 · ingesting daily
How we start
The first month is designed so you can walk away from it and still be better off.
A written scope
What gets built, what does not, what it costs. Yours to keep — take it to another vendor if you like.
One working slice
Deployed in your accounts and used by one real person on your team. Not a prototype, not a deck.
Two-week cycles
Demo, written notes, invoice for the next cycle. Every cycle ends with something running, so stopping is never expensive.
Each boundary is an exit you can take without losing anything.
Straight answers
The questions we get asked in the second email. Answered here instead.
You are 10,000 km away. What happens if you disappear?
The code lives in your repository and runs in your cloud account from the first week — we cannot hold your system hostage, because we are never the only ones holding it. Every cycle also produces a written runbook, so another team can pick it up without talking to us.
Why Kyrgyzstan?
It is where we live. Bishkek has a small, experienced engineering community and costs a fraction of a US city, which is why a senior team is affordable here. We say it plainly because you will find out anyway, and a company that hides its address has told you something.
How does GMT+6 work against US hours?
Our afternoon overlaps your morning — roughly three hours with the US East Coast. We plan for that instead of pretending it away: written updates land before your day starts, and calls, when you want them, sit in that window.
What do you not do?
Marketing sites, mobile apps as products, staffing by the seat, and anything where the plan is to hand us a specification and check back in six months. We build systems people use at work, with the people who use them.
Why is there no team page?
Because headshots prove nothing. The two people who do the work write every message you receive — no account manager in between.
OfflineTasks is public, and so are its rough edges.
A Windows maintenance tool that runs cleanup jobs at the one moment they always work — right after reboot, before anything can lock a file. Its README opens with what the tool deliberately cannot do: no arbitrary commands, no network, no persistence. Commit history, issues and all.
Open source at Ferwyn →- MIT
- PowerShell · JSON
- Housekeeping across many machines, made predictable and hands-off.
Have a system that needs building?
Send us the shape of the problem. If we are not the right fit, we will say so and point you somewhere better.
Start a project- A reply from one of us within 1 business day.
- Questions in writing — no discovery call unless you want one.
- A written scope with a price, or an honest no.