usable.software

Monday, 07:12. Is the rebar sign-off happening or not?

The answer lives in a WhatsApp group, in two schedules that disagree, on a sticky note on someone's monitor — and in the head of a person who is currently on the phone. The site still runs. But every answer costs three follow-up questions, and nobody can say which version is true.

On top of that comes the thing no site can argue away: the crew speaks Polish, the subcontractor Romanian, the site manager German. An instruction nobody reads reliably isn't an instruction.

That's the normal state of affairs in an uncomfortable number of companies. Not through incompetence — but because the alternatives have been either an ERP bigger than the problem, or a software project with a requirements document, six months of runway and an open end.

Usable is the third option.

Assembled, not generated

Usable is a closed kit. Every module is fully built, tested and maintained — by people, not by a prompt. Your system doesn't come into being because somebody starts coding; it comes into being because you assemble what already exists.

That's the whole difference from the two extremes the market is currently swinging between:

• →No AI-generated code. What runs in a demo doesn't carry a business. Generated systems have no owner, no test coverage and nobody who still understands them in two years.
• →No off-the-shelf no-code kit. Those end up either as Excel with a nicer surface, or as a contraption that breaks on the first real requirement.
• →No six-month project. There is nothing to develop. The building blocks exist.

Engineered properly, not generated — and therefore ready in minutes rather than months.

How the system is cut

Three levels. Understand them once and the rest explains itself:

Vertical — your shelf. A vertical is an industry. It determines which modules are on the shelf at all and what they're called: in construction a job is a site, a measurement, a variation — not a "resource" and a "process object".

Core — always included, never optional, never billed separately: dashboard, user management, settings and audit log. No system is usable without those four, so they're in the base price.

Modules — the clickable part. Sites, scheduling, measuring, site diary, defects, equipment, purchasing, time tracking, team chat. You pick only what your business actually needs. The rest stays on the shelf — available, but not in your system and not on your invoice.

Underneath sits a cross-cutting layer you never configure, because it isn't a product but a foundation: roles and permissions down to the data-row level, audit log, GDPR tooling, notifications, tenant isolation. Built hard once, reliable everywhere.

The real trick is one level deeper: modules don't couple to each other, they couple to data entities they provide or require. That's why adding or dropping modules doesn't explode into variants — the orthogonality is structural, not the product of discipline.

Everyone reads it in their own language

Construction crews rarely share one language. So multilingualism in Usable isn't a translation file added later — it's part of the configuration:

• →Interface per person. Every user gets the system in their own language — on the phone on site just as much as in the browser in the office. The foreman sees "Sprawdzić zbrojenie", the site manager sees the same task as "Check rebar".
• →Team chat with automatic translation. Messages arrive in the recipient's language. Write in German, get read in Polish — without anyone propping a translation app next to it.
• →Main language. It sets documentation, welcome emails and the app default for new people.
• →Two languages are included, eight available. Each additional one costs a fixed amount per language per month — no quote, no project.

That's the difference between "we have an app" and "the crew actually uses it".

Minutes instead of months

1. 01Pick a vertical — the cut for your industry.
2. 02Click the modules — the configurator prices it live, checks dependencies and tells you when a module needs something that isn't there yet.
3. 03Set the shape — web, mobile or both, languages, custom fields, data location, branding.

Custom fields are added without rebuilding the database. Data sits in the EU by default, or in a dedicated instance in Germany on request. For branding your website address is enough: Usable pulls the logo, brand colour and company name and lays them over the system. Before you order, you click through a branded preview of your actual system — a typical screen per module: list, board, calendar, chat, gallery, form.

No requirements document. No quote request. No sales call that happens in two weeks' time.

What comes after — and what stops happening

After launch the configurator stays your control panel: the same interface shows you the difference from your current setup and what it costs before you confirm. Add a module, drop a module, add a language when a new crew starts — no ticket, no quote, no project.

What doesn't happen: your system standing still. Modules are versioned individually and developed centrally; improvements and security updates flow into your instance automatically. You don't get the version from your go-live day and then live with it for five years.

Where it runs, and who owns it

Two routes:

• →Hosted by us — ready to go at your own address (`yourcompany.usable.works`) or your own domain, hosting and maintenance included. Heavy usage (many users, lots of storage) adds a usage-based share.
• →Self-hosted — you get a sealed container plus a licence and run it on your own infrastructure. Monthly licence and updates; the running costs sit with you, and we don't resell hosting.

Either way: your data is yours and exportable at any time. Rented here means cancel monthly — not an annual contract with a notice period. Whoever leaves takes their data with them; that's the one promise you can actually measure a vendor against.

Who this is built for

For businesses between five and two hundred people whose process is sound but whose tooling isn't:

• →Construction and fit-out — sites, scheduling, measuring, site diary, defects, variations, equipment
• →Trades and maintenance — jobs, appointments, materials, service intervals, proof of work
• →Companies with multilingual crews and subcontractors — anywhere an instruction and its record have to land, whoever reads them

The common thread: the work is already organised. It's just spread across four tools, none of which was built for it.

What stays the same — and what gets better

The work doesn't change. The path to reliable information gets shorter.

• →*Where does the site stand?* — the status is visible instead of scattered across messages and calls.
• →*Is the variation documented?* — measurement and photo hang off the job, not in the camera roll of someone who's off today.
• →*Which deadline is next?* — the system speaks up beforehand. Not two weeks after the inspection lapsed.
• →*Did the crew understand it?* — they read it in their language and signed it off.

Status

Usable is being built. If your industry is missing, a short call is worth it — new verticals get their shape from real businesses, not from a drawing board.