Skip to content

What Blok is ​

Blok runs the operational side of a construction or field-services company: the work that gets requested, scheduled, done, documented, and billed.

It replaces the common stack of a project board, an automation tool, and a separate forms app. That's not because those tools are bad, but because splitting one process across three of them means the process itself lives nowhere. A work order's status is on the board, the rule that moves it is in the automation tool, and the photos proving it happened are in the forms app.

The loop it's built around ​

Request  →  Approve  →  Dispatch  →  Crew does the work  →  Review  →  Invoice

Everything else supports that loop:

  • Work orders carry the job through it
  • Forms capture what happened in the field (photos, hours, materials, signatures), offline if there's no signal
  • Estimates win the work in the first place
  • Invoices bill it, with the field documentation attached
  • Timesheets turn the same captured hours into payroll

Because the loop is one system, the hours a crew enters on a form become the labour line on the invoice and the hours on the timesheet, without anyone retyping them.

What makes it configurable ​

Blok is multi-tenant: several companies run on it, each with different terminology and process. Rather than fork the product per customer, the parts that differ are configuration:

  • statuses and their order
  • work-order types, and which form each one opens
  • custom fields on any entity
  • billing rates, per customer or per project
  • which fields appear on a detail page, and in what arrangement

A blueprint bundles all of that into one file so a new organization starts configured. See Blueprints.

What it deliberately doesn't do ​

  • It isn't accounting. Invoices sync to QuickBooks; the books stay there.
  • It isn't payroll. Timesheets produce hours; pay runs elsewhere.
  • It isn't a CRM. There's a light lead pipeline, not a sales suite.

Each of those is a system a company already has and trusts. Blok's job is to feed them accurate data, not replace them.

Internal documentation. Not for distribution.