Services

What we build and run

Six kinds of work, one subscription. Everything below is priced the same way: by the number of screens, with hosting and maintenance included.

Custom web applications

Software shaped to how your company actually works.

Quoting, orders, scheduling, case tracking, approvals: the processes that make your business different are the ones off-the-shelf software handles worst. We build them as a web application with React front ends, Node APIs, and Postgres, deployed to an AWS account in your name.

You start with a click-through prototype, then get working software every 1 to 3 weeks. Screens are priced by count, so adding scope is a line item on the monthly fee.

Good fit when you have

  • A process that lives in three tools and a lot of copy and paste
  • Rules only one person knows how to apply
  • Reports assembled by hand every week

Customer and partner portals

Let customers help themselves, on your terms.

Give customers, vendors, or partners a place to sign in and do things themselves: check status, submit requests, download documents, update their details. Your team answers fewer emails and phone calls, and customers get answers at 9pm.

Login runs through a managed identity provider, so accounts, password resets, and access rules are handled properly from day one. Each portal screen is one dynamic screen.

Good fit when you have

  • The same status questions arriving by phone and email
  • Documents sent as attachments and lost
  • Partners who need a slice of your data, not all of it

Internal tools

Retire the spreadsheet everyone is afraid to touch.

Replace the spreadsheet everyone edits, the shared inbox that tracks requests, or the desktop database only one person understands. Internal tools are usually where a custom app pays for itself fastest, because the time they save shows up every single day.

Staff sign in with the directory they already use. Roles control who sees what. Lists, forms, and dashboards each count as one screen, whether they hold ten fields or fifty.

Good fit when you have

  • A spreadsheet with tabs nobody dares delete
  • Requests tracked in a shared inbox
  • A desktop database that cannot be opened from home

Integrations and migration

Connect what you have, or move off it cleanly.

Most businesses already keep data somewhere: a FileMaker system, an accounting package, a CRM, a vendor API. We connect to it, sync with it, or move off it, depending on what you need, so the new application starts with your real records instead of an empty database.

For migrations, we map the data, test the import against real records, and recommend you keep the old system running until you confirm the new one is right.

Good fit when you have

  • A FileMaker system that needs a web front end
  • Orders re-keyed into accounting by hand
  • Two systems that disagree about the same customer

Cloud hosting in your account

Your app, your cloud account, our operations.

Your app runs in an AWS account that belongs to you. Static pages use static hosting. Dynamic apps run as a containerized Node API with managed Postgres. A managed identity provider handles login. Nothing is hidden inside our infrastructure.

Backups are encrypted with retained snapshots. Deployment is one click once staging passes. AWS bills you directly for usage, and cost is reviewed in every quarterly audit.

Good fit when you have

  • You want to own the infrastructure, not rent it through a vendor
  • Finance wants the cloud bill on your own account
  • You have been burned by a platform shutting down

Maintenance plan

Included in every subscription, not sold on top.

Software you stop maintaining becomes a liability within months. Packages age, advisories pile up, certificates expire. The plan keeps your app patched, current with your cloud provider, and backed up, without a separate support contract.

It includes continuous dependency scanning with weekly triage, tracking of cloud advisories and deprecations, urgent escalation with a recommended action and cost estimate before work starts, and a quarterly audit across ten engineering dimensions with a written report.

Good fit when you have

  • An app nobody has updated since it launched
  • A cloud bill nobody has looked at in a year
  • No idea whether the backups would actually restore

Most projects mix two or three of these

Describe what you are trying to do and we will sort it into screens with you. You do not need to pick a category first.