Custom applications

Software built to fit how your organization actually runs.

We build software for your organization when nothing off the shelf fits: scheduling tools, member portals, notification systems and the internal applications that replace a spreadsheet. They are web applications that work on every phone and desktop, built on AWS, handed over with the source code, the documentation and the infrastructure definitions. Scoped in a fixed-price discovery sprint from $2,500, built in two-week increments, and yours at the end. Sometimes the right answer is a subscription that already exists, and the sprint says so in writing.

What we build

The shapes that come up most.

Scheduling and coordination

Assignments, availability, changes and confirmations for people who are not at a desk. Replaces the group text and the whiteboard, or connects the product you already pay for to the rest of what you run.

Member and customer portals

One place to log in, see status, submit a request, pay a fee, download a document.

Communication and notifications

The right message to the right people at the right moment, by email or text, with a record of who was told what.

Internal applications

The spreadsheet everyone is afraid to touch, rebuilt as a system with permissions, history and backups.

Integrations between systems you already own

ERP to CRM, accounting to field service, forms to the database, the subscription you bought to the reports it lacks. Data entered once.

AI features inside the application

Document extraction, search over your own files, drafting help, where they pay for themselves and nowhere else.

How a project runs

A number on paper before you commit to a build.

  1. A 30-minute call

    You describe the problem. We ask who uses it today, what goes wrong, and what already exists: a spreadsheet, a current tool, a quote from someone else.

  2. A discovery sprint, fixed price

    One week at $2,500 for a small organization; two weeks at $5,000 when there are systems to integrate. Screens, data model, integrations, hosting estimate and a build quote, written down. If the answer is that an off-the-shelf product fits, we name it and its price, and we quote the work of connecting it to what you already run. The sprint fee comes off the first build invoice if the build starts within 90 days.

  3. Build in two-week increments

    Something working to click on every two weeks, hosted in an account you own, with the people who will use it looking at it early.

  4. Handover or retainer

    Your choice. Either way the code, the data and the cloud account are yours.

What you receive at handover
  • The source code, in a repository you own.
  • The infrastructure as code that builds the hosting environment.
  • Documentation and a runbook for the person who keeps it running.
  • The cloud account in your name, with the bills going to you.
  • A handover session, recorded if you want it.
  • A retainer from $750 a month if you want us to keep operating it. Your choice, not a condition.
How we price

The discovery sprint is fixed: $2,500 for one week, $5,000 for two weeks with integrations, and the whole fee is credited against the build if the build starts within 90 days. Builds are fixed price wherever the scope can be bounded, which discovery exists to make possible, and time and materials only where it genuinely cannot be, with an hours report. Half of any fixed-price build is invoiced at signature, the balance at acceptance against the criteria written into the statement of work, net 15. No work starts without a signed statement of work.

Two smaller engagements

Review and harden what you built, fixed price from $1,500: a read of the code and the hosting, the identity, backup and logging gaps, and a written list of what to fix with the fixes quoted. Connect the product you bought to what you already run and build the reports it lacks, scoped in the same discovery sprint.

Proof

We built and ran software of our own.

CloudStack Canvas was a multi-tenant SaaS product with organizations and seats, subscription billing, and an engine that turned architecture diagrams into deployable cloud infrastructure. Designed, deployed and operated on AWS, then retired when AI coding agents made its core job a commodity.

It is why the handover list above is specific: it is what we would want handed to us. And it is why we will tell you when a subscription beats a build; we have made that call about our own product.

Built the same way as the AI work

Identity for every user, logging for every action, backups you can restore from, and data that stays in your account. No AI coding agent ever holds production credentials in your account: production changes are applied by a person, with a second reviewer, from a role scoped to the change. The same practice that regulated environments require, applied just the same to a scheduling tool for a volunteer association, because the habits do not change with the size of the client.

Questions we hear first

Before you ask.

Do we own the code?

Yes, all of it. The repository, the infrastructure definitions and the data are yours from the first commit. We keep only our own generic tooling and know-how, which the statement of work spells out.

Can you take over, fix or harden an application someone else built, including one we built ourselves with an AI tool?

Yes. The review starts at $1,500: we read the code and where it runs, check identity, backups, logging and what the application exposes, and give you a written list of what to fix with the fixes quoted. We tell you plainly whether repairing it or replacing it is the cheaper path.

Do you build native iPhone and Android apps?

We build web applications that work on every phone and desktop and can be installed to the home screen. For most scheduling, portal and communication tools that is the right answer. If a project truly needs a native app, we say so up front rather than build one badly.

How long does a first version take?

Discovery takes one to two weeks and ends with a written scope and quote. Once a build starts there is something working to click on every two weeks. The total depends on the scope that discovery produces, which is the point of doing discovery first.

What does it cost?

The discovery sprint is fixed: $2,500 for one week for a small organization, $5,000 for two weeks when there are systems to integrate, and the whole fee comes off the first build invoice if the build starts within 90 days. The build itself is quoted at the end of the sprint, because no two are alike and a number before discovery is a guess. If you have a budget range in mind, the quote form has a place for it, and it helps us scope to what you can actually spend.

What does hosting cost after launch?

The application runs in your own AWS account, so AWS bills you directly and we never mark it up. Discovery includes an estimate of monthly running cost for the scope we propose. Small applications for small organizations are usually tens of dollars a month.

Tell us what it should do.

A few sentences are plenty. We reply within one business day with questions or a time to talk.