HPO Software4D & low-code application studio
4D · low-code · database applications

Business software that fits the way you already work.

HPO Software designs, builds and maintains custom database applications on 4D and modern low-code stacks — order systems, inventory, scheduling, CRM and reporting tools for teams that have outgrown spreadsheets but don’t fit an off-the-shelf product.

  • New builds & upgrades
  • You own the code
  • Remote, worldwide
What we build

From one critical screen to the whole back office.

Most projects start with a single painful workflow. We model the data properly first, so the second and third workflows are cheap.

Custom 4D applications

Desktop, client/server and web apps on a single 4D codebase — orders, stock, jobs, billing and the reports your managers actually read. Designed around your process, not a template.

  • ORDA data model
  • Client/server
  • Role-based access

Legacy upgrades

Move an older 4D application to a current LTS release: refactor deprecated commands, convert to project mode, add source control.

Web & mobile front-ends

Expose your existing 4D data through REST and a clean browser UI, so field staff and customers can use it without a desktop client.

Data migrations

FileMaker, Access, Excel and old SQL schemas into a normalised model — with reconciliation reports so nothing silently disappears.

Integrations

Accounting, e-commerce, shipping and email services connected through documented APIs and scheduled jobs.

Support & maintenance

A named developer who knows your application, a ticket queue, and monthly release windows. Upgrades are planned, not discovered.

uptime checks · backups verified · release notes

Effort estimator

How big is your application?

Move the sliders to describe what you need. You’ll get a rough effort band and the kind of engagement that usually fits. It’s a starting point for a conversation, not a quote.

Rule of thumb we use: tables drive the data model, screens and reports drive build time, integrations add risk.

Rough effort
8–12 weeks
Usually fits
Fixed-scope build
How a project runs

Small releases, visible progress.

  1. $ hpo scopeScope & schemaTwo to three workshops. We map the workflow, agree the data model and write down what “done” means.
  2. $ hpo build --sprintBuild in sprintsWorking screens every two weeks on a test server you can click through, with notes on what changed.
  3. $ hpo migrate --verifyMigrate & verifyTrial migrations with row counts and spot checks signed off by your team before go-live.
  4. $ hpo handoverHandoverSource, documentation and an admin guide. Stay on support, or take it in-house — your call.
Choosing a route

Spreadsheet, SaaS or a custom app?

Custom isn’t always the answer. Here’s how we talk clients through it.

SpreadsheetsOff-the-shelf SaaSCustom 4D app
Fits an unusual processPartly, by handOnly if it matches the vendor’s modelBuilt around it
Multi-user with permissionsFragileYesYes
Where your data livesFiles on drivesThe vendor’s cloudYour server or your cloud
Cost profileCheap until it breaksPer-seat subscriptionBuild cost + optional support
Time to first versionDaysDays to weeksWeeks
Engagement models

Pick the shape that matches the risk.

Most common

Fixed-scope build

A defined first release with a fixed price agreed after scoping. Change requests are estimated before they’re done.

2–6 weeks

Upgrade sprint

Bring an existing 4D application onto a supported release, fix what breaks, and leave it under source control.

Monthly

Support retainer

A block of developer hours each month for fixes, small features and release management, with a named contact.

FAQ

Before you ask.

Do you only work with 4D?

4D is our specialty, but we also build on low-code platforms and plain web stacks when they fit better. We’ll say so during scoping.

Can you take over an application someone else built?

Yes. We start with a short code review and a written list of risks before quoting any changes.

Who owns the code?

You do. Source and documentation are handed over at the end of each release.

Do you work with teams outside the US?

Yes — all of our work is remote, with overlap hours agreed at the start.

Next step

Tell us about the workflow that hurts most.

Send a short description — screens, users, where the data lives today. You’ll get a reply with questions or a proposal for a scoping session.

Nathan AndersonSolutions Lead
nanderson@hposoft.comContact Nathan