ContactBook a call

How projects run

How we work

The systems and habits behind every build. What we use, what it shows you, and what stops mistakes reaching your customers.

The screens on this page are from our own tools. They show a demo project, Demo Harbour Coffee app, with demo data and demo names. They never show a client's work.

01 / 06

A portal for every client

Each client signs in to their own portal to see the project's progress, milestones and dates, the updates we post, the files we share and a message thread with the team.

Sign-off requests are answered there, and every sign-off writes a receipt sent to both sides. Clients can sign in with two-factor codes or a passkey (a fingerprint, face or device PIN).

Inside a client portalA diagram, not a screenshot

  • Progress and datesMilestones, and where each one stands.
  • UpdatesPosted by the team as the work moves.
  • FilesShared with you in one place.
  • MessagesOne thread with the team.
  • Sign-offsRequests you answer right there.
  1. Step 1We askA sign-off request appears in your portal.
  2. Step 2You answerYou reply there, so the decision is not lost in an inbox.
  3. Step 3Both sides get a receiptEvery sign-off writes a receipt, sent to you and to us.

02 / 06

Every task written down

We built our own project system, called Work. Every task is an issue with a key, an owner, a status, a priority, an estimate and a full history.

There are boards, a backlog and sprints, a timeline of epics, dates and milestones, and time logged against each issue. Nothing lives in someone's head or a chat thread.

The Work board for the demo project. DHC Sprint 2 is running, with its goal, and issues sit in Backlog, To do, In progress, In review and Done columns, each card showing a key, an owner, points and a due date.
The board: the running sprint, its goal, and every issue by status.Open full size (opens in a new tab)
One issue open over the board: DHC-13, Pay with a saved card, showing its status, assignee, priority, due date, sprint, labels, a two day estimate and one day two hours logged against it.
One issue open: owner, status, priority, dates, estimate and the time logged against it. Its full history sits underneath.Open full size (opens in a new tab)
The Work timeline for the demo project: epics and their issues drawn as bars across weeks, with the two sprints and a milestone called Beta to testers marked, and a line for today.
The timeline: epics, their issues, sprints and milestones against dates.Open full size (opens in a new tab)

03 / 06

Reports that show where the time went

The issue history feeds a full set of reports. They are interactive and exportable, with a table and a CSV behind each one.

We can show a client where the time went.

The reports

  • Burndown
  • Burn-up
  • Velocity
  • Cumulative flow
  • Cycle time and lead time
  • Throughput
  • Ageing work
  • Created vs resolved
  • Epic progress
  • Time against estimates
The reports hub for the demo project: burndown, burn-up and velocity charts for the sprints, each with a one line summary and a link to open the full report.
The reports hub: each chart opens into its own report.Open full size (opens in a new tab)
The cumulative flow report: stacked bands of done, in progress and to do issues over thirty days, with range, grouping and filter controls above it and a Download CSV button.
One report open: cumulative flow, with its range and filters, and a CSV download.Open full size (opens in a new tab)

04 / 06

Checks before anything goes live

Every change goes through automatic checks before it can go live, and a failing check blocks the release.

Changes are tried somewhere safe first, and database changes are rehearsed before they touch the real thing.

  • Automatic checks

    Type checks, linting and automated tests run on every change.

    A failing check blocks the release.

  • Review

    Larger releases are reviewed before they ship.

  • Staging first

    Changes run on a private staging copy of the system.

    It holds anonymised data, never real personal information.

  • Database changes

    Rehearsed on a copy of the real data before they touch it.

    A fresh backup is taken first.

05 / 06

Safety nets

We plan for things going wrong. Backups are taken every night and restores are tested, and if something breaks the team gets an alert within minutes.

Nightly backups
The database and the uploaded files are backed up every night and kept for 35 days. Restores are tested, not assumed.
Point-in-time recovery
The database can be recovered to a chosen moment, not only to the last nightly backup.
Error monitoring
Errors are watched, and the team gets an alert within minutes when something breaks.
A public health check
Anyone can open digitalkatalyst.us/api/health to see whether the system is answering.
A change history on every record
Every record keeps its history, so nothing is lost silently.
Separate, locked-down addresses
The client portal and our team console each run on their own address, apart from this website, with strict security rules and sign-in by passkey or two-factor codes.

06 / 06

One lead, everything recorded

You always know who to talk to. Every project has one named lead as your point of contact, and Imtinan Farooq, our founder and lead engineer, leads the team.

  • Point of contact

    A named lead

    One person to ask, so you are never working out who to contact.

  • Updates

    Posted to your portal

    Updates are written down where you can read them.

  • Decisions

    On the record

    Decisions and sign-offs are recorded, so there is something to point back to.

Ask us how this would run on your project.

The first conversation is free and jargon-free, and you'll leave with a clear next step either way.