Services / Software Development
Software that removes a step from someone's day.
Internal tools, portals, integrations and automations, built by a team that has run operations and knows which manual steps hurt. Delivered in milestones of a few weeks, each one ending with something that works.
Milestones you can use, not phases you wait through.
We don't do a six-month build followed by a big reveal. Every two to four weeks something ships to a staging environment, you use it, and the next milestone is planned from what you learned.
- Discovery, one week. We watch the process you want to change, list the systems involved, and write the scope for milestone one. Fixed price on that milestone only.
- Milestone one. The smallest version that removes the manual step for one real user. Usually three weeks.
- Milestones two onward. Each scoped from the previous one. You can stop after any of them with working software.
- Handover or retain. Documentation, deployment runbook and a walkthrough for your team; or a support retainer with us.
The things clients usually ask for first.
Each of these started as "someone spends a day a week doing this by hand."
An order-exceptions dashboard
Pulls failed and stuck orders from the store and the shipping system into one screen, with the fix actions built in. Replaced a spreadsheet and a morning of copy-paste.
Practice system to accounting sync
Posts daily payments and adjustments from a practice management system into the accounting ledger, reconciled, so month-end stops starting with a data export.
Document intake with extraction
Reads incoming PDFs from a shared inbox, extracts the fields that matter, files them to the right record, and flags the ones it isn't sure about for a person.
A client portal for a services firm
Clients upload documents, see status and download deliverables without emailing anyone. Built on the firm's existing systems, not beside them.
What you'll notice in the first week.
- Repository
- Yours from day one. Every change is a reviewed pull request with a description a non-developer can read.
- Environments
- Staging you can log into at any time. Nothing reaches production without your sign-off on staging.
- Communication
- A shared channel, a weekly written update, and a demo at the end of each milestone. No status meetings for their own sake.
- Testing
- Automated tests on the parts that would hurt if they broke; a written test plan for the rest, run before every release.
- Security
- Secrets in a vault, dependencies scanned, access by named accounts. Same rules as our IT and operations teams.
Questions
What kind of software do you build?
Mostly the unglamorous kind that makes a business run: internal tools, customer portals, integrations between systems that don't talk to each other, and automations that remove a manual step. We also build products, but we'll tell you honestly if what you need is an off-the-shelf tool.
Which technologies?
TypeScript and Node on the back end, React or Astro on the front, Postgres for data, hosted on AWS or Cloudflare. Python where it fits, particularly for data and AI work. We choose boring, well-supported tools so your next developer can pick it up.
How do you price a project?
Fixed price per milestone against a written scope. Each milestone ends with working software you can use, not a document. If scope changes, the next milestone is re-quoted before it starts, in writing.
Who owns the code?
You do, from the first commit. The repository is in your organization, we work in it, and the licence for everything we write is assigned to you in the contract.
What about after it launches?
A monthly support retainer if you want one, covering fixes, small changes and dependency updates. Or a handover and documentation package if your own team is taking it on.