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 someone who's on the phone right now. The site keeps running. But every answer costs three follow-up questions, and nobody can say which version is right.

Then there's the thing no site can argue away: the crew speaks Polish, the subcontractor Romanian, the site manager German. An instruction nobody can read with confidence isn't an instruction.

That's normal in an uncomfortable number of companies, and it has nothing to do with incompetence. Until now the alternatives were an ERP bigger than the problem, or a software project with a requirements document, six months of runway and no clear end.

Usable is the third option.

Assembled, not generated

Usable is a closed kit. Every module is fully built, tested and maintained, by people rather than by a prompt. Your system doesn't come about because somebody starts coding. It comes about because you assemble what already exists.

That's what sets it apart from the two extremes the market keeps swinging between:

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

Properly engineered rather than generated, and so ready in minutes rather than months.

How the system is structured

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

Vertical: your shelf. A vertical is an industry. It decides 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” or 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 part you click. Sites, scheduling, measurements, 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's the foundation rather than a product: roles and permissions down to individual data rows, audit log, GDPR tools, notifications, tenant isolation. Built solidly 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 need. That's why adding or dropping modules doesn't explode into variants. The modules stay independent because the structure enforces it, not because everyone is being disciplined.

Everyone reads it in their own language

Construction crews rarely share one language. So multilingual support in Usable isn't a translation file that shows up later. It's part of the configuration:

• →Interface per person. Every user gets the system in their own language, on a phone on site just as much as in a 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 the documentation, welcome emails and the app default for new people.
• →Two languages 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 your logo, brand color and company name and applies them to the system. Before you order, you click through a branded preview of your actual system, with a typical screen per module: list, board, calendar, chat, gallery, form.

No requirements document. No request for a quote. No sales call that happens two weeks from now.

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, and 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, with 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 license and run it on your own infrastructure. You pay monthly for the license and updates. The running costs sit with you, and we don't resell hosting.

Either way, your data is yours and can be exported at any time. Rented here means cancellable monthly, not an annual contract with a notice period. Whoever leaves takes their data with them. That's the one promise you can really measure a vendor against.

Who this is built for

For businesses of five to two hundred people whose process is sound but whose tools aren't:

• →Construction and fit-out: sites, scheduling, measurements, 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 organized. 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 in one place 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 take their shape from real businesses, not from a drawing board.