Billing and point-of-sale
Fast keyboard-first billing at the counter, with thermal printers, cash drawers, and barcode scanners.
Desktop applications
Windows software for the counter, the office, and the shop floor.
Overview
Some work still happens at a desk or a counter, often on a patchy connection and next to a printer or a scanner. We build desktop software that keeps working offline and syncs with your server when it can.
What you get
- Windows apps, with macOS and Linux when needed
- Offline-first, with sync to your server
- Installers and automatic updates
- Printers, scanners, and barcode readers
What we offer
Desktop applications, in detail
Pick the parts you need. We scope them together, quote a fixed price, and build in two-week steps.
Shop-floor terminals
Simple screens for production entry, weighing scales, and label printing, built to be used with gloves on.
Offline with sync
The app keeps a local database and syncs with your central server when the connection allows, so a network cut never stops the counter.
Hardware integration
Printers, scanners, weighing scales, RFID readers, and machine controllers over USB, serial, and network.
Installers and updates
Signed installers and automatic updates, so you never walk from PC to PC with a USB stick.
Modernising old desktop software
VB6, FoxPro, and old .NET applications moved onto a supported platform without losing years of data.
Where it fits
Typical projects
- Counter billing for a retail chain that must work through outages
- Weighbridge and dispatch terminals at a plant gate
- Label and barcode printing on a packing line
- Replacing a FoxPro system the original developer no longer supports
Technology
What we use
Well-supported tools with a long runway, chosen for the project rather than for novelty.
- .NET
- WPF
- WinUI
- Electron
- Tauri
- SQLite
- SQL Server
Where AI fits in
Desktop software can use AI to read scanned documents, suggest item codes as you type, and flag entries that look wrong before they are saved.
How it works
From first call to production
Every engagement follows the same shape, so you always know what happens next and what you will see.
- 01 · Week 1
Scope
We sit with the people who will use the thing. You get a written scope, a fixed estimate, and an honest note about what we would cut first.
- 02 · Weeks 2 to 10
Build
Two-week iterations against a shared board. You see working software every fortnight, not a status deck.
- 03 · Launch week
Launch
Staged rollout, real monitoring, and a rehearsed way back. We stay on the call until the graphs go flat.
- 04 · Ongoing
Run
Patching, alerts, and a monthly review of cost and reliability. Leave with your code and your documentation whenever you want.
Questions
Frequently asked questions
Why desktop instead of a web app?
Desktop software is the better choice when it must keep working without internet, talk directly to hardware, or be very fast at a counter. When none of that applies, we will usually recommend a web app.
Can it run on old PCs?
Usually, yes. We test on the hardware you actually have and keep the app light enough for it.
Can you take over our existing desktop software?
Yes. We review the code and data first, then either maintain it, upgrade it in place, or plan a staged rewrite.
Related
More from Build
Have a project like this in mind?
Send a paragraph about what you need. An engineer replies within one working day, and you get a written scope with a fixed price within a week.