DenaliWorkflow Systems
Describe the problem

Custom software · Fairbanks, Alaska · working anywhere

Software for the work you’re still doing by hand.

We build custom tools, automation and full products, wherever they need to run: in the cloud, on your own server, on a phone or offline. We start from the job, not the tech, and hand over something that keeps working.

Describe the problemSee what we’ve built
  • In the cloud
  • On your own server
  • On a phone
  • Offline
  • On the desktop
  • Live, in real time

Sound familiar?

If it’s done by hand every week, it can probably be built.

Slow work is rarely about lazy people or the wrong app. It’s a workflow problem: information that has to be carried from one place to another by somebody, over and over.

  1. Mon 08:00The weekly report someone rebuilds by hand, from four exports.fixable
  2. DailyOrders copied out of email and typed into the system, one by one.fixable
  3. AlwaysA spreadsheet with rules only one person understands.fixable
  4. UsuallyReminders that go out if somebody remembers to send them.fixable
  5. Per clientThree apps that each hold a third of the customer.fixable
  6. Since 2019The tool everyone hates and nobody can replace.fixable

What we build

Seven kinds of software. One way of working.

Every one of these is backed by something we’ve actually shipped.

What we build, and where it runs

Featured work · Live, with paying customers

Families, schedules, attendance, progress reports, texting, staff hours and billing, in one place instead of six. Each center gets its own address and its own database, and the rules send reminders and follow-ups on their own.

10
kinds of center on one product
~6,500
automated tests
1
separate database per center
~2 wks
between releases
How CenterSuite is built
CenterSuite’s weekly classroom schedule, with students listed by room and half-hour slot, color-coded by subject, capacity counts under each slot and absences struck through. The names are demo data.
A printable CenterSuite progress summary for a demo student, with a chart of their math level climbing steadily over two years.
All the work: ten projects and an arcade

How it goes

Small stages, real progress every week.

  1. 01

    Watch the work

    We sit with the job as it really happens, workarounds and all, before anyone talks about software.

  2. 02

    Prove the hard part

    The riskiest piece gets built first, small and working, so surprises turn up early and cheaply.

  3. 03

    Ship in stages

    You use each stage as it lands. Every week there’s something real to look at, not a status report.

  4. 04

    Keep it running

    Tests, backups, monitoring and documentation, so it still works next year, with or without us.

How projects work, and what they cost

Built to keep working

Software people rely on has to survive Tuesday.

The interesting part of a system is what happens when something goes wrong. These are the habits that make ours boring in the best way.

Notes

Notes from the workbench.

All notes
  1. Workflow problemsWhen a spreadsheet should become an appSpreadsheets are brilliant until they quietly become the system your business runs on. Six signs it’s time, and what to keep when you move.
  2. Where software runsSelf-hosted, cloud or on-device: where software should runWhere a piece of software runs shapes its cost, its privacy and what happens when the internet drops. How we choose, with three real examples.
  3. Building to lastSoftware that fails gracefullyEvery system breaks somewhere. The good ones keep working when a piece fails. Four habits we build in, and where they’ve saved the day.

Next step

What’s the job you’d like to stop doing by hand?

Describe the problem in a few sentences. Within one working day you’ll hear whether software would fix it, roughly what it would take, and what we’d look at first.

Describe the problemor email sales@denaliws.com