Software built to fit how your organization actually runs.
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, built in two-week increments, and yours at the end.
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.
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. 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.
A number on paper before you commit to a build.
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.
A discovery sprint, fixed price
One to two weeks. Screens, data model, integrations, hosting estimate and a build quote, written down. If the answer is that an off-the-shelf product fits, we say so.
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.
Handover or retainer
Your choice. Either way the code, the data and the cloud account are yours.
- 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 if you want us to keep operating it. Your choice, not a condition.
Fixed price wherever the scope can be bounded, which discovery exists to make possible. Time and materials in 40- or 80-hour blocks where it cannot. Half of any fixed-price build is invoiced at signature, the balance at acceptance, net 15. No work starts without a signed statement of work.
We run software of our own.
CloudStack Canvas is a live, multi-tenant SaaS product with organizations and seats, subscription billing, and an engine that turns architecture diagrams into deployable cloud infrastructure. Designed, deployed and operated on AWS in-house.
It is the clearest proof we can offer that we finish what we start and keep it running afterward, and it is why the handover list above is specific: it is what we would want handed to us.
Identity for every user, logging for every action, backups you can restore from, and data that stays in your account. The same practice that regulated environments require, applied to a scheduling tool for forty volunteers, because the habits do not change with the size of the client.
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 or fix an application someone else built?
Often. We start with a short review of the code and where it runs, and we tell you plainly whether repairing it or replacing it is the cheaper path. Sometimes the honest answer is the second one.
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?
No two are alike, so we do not publish a number. The discovery sprint is fixed price and produces the build quote. 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 is plenty. We reply within one business day with questions or a time to talk.