SMRIT LABZ  —  Rooted in Wisdom, Driven by Innovation.

Approach

Why we build for how each industry actually works

SMRIT LABZ starts from an industry’s real operating conditions, its rules, people and daily routines, before designing a system. What that means in practice.

SMRIT LABZ · · 4 minute read

A site engineer and an operations manager reviewing plans on a tablet at a construction site

Most technology is sold the same way to every customer. A system built for one kind of business is offered to all of them, with a different logo on the brochure and a list of settings to adjust. Sometimes that works. Often it does not, and the people who pay for the gap are the ones using the system every day.

At SMRIT LABZ we start somewhere else: with how a particular industry actually operates. Our name for this is industry-native. This note explains what we mean by it and why we think it matters.

A hospital is not a shop, and a school is not a factory

On paper, many industries need the same things: scheduling, records, payments, communication with customers. In practice, each industry wraps those needs in its own conditions.

  • In healthcare, a message to a patient is governed by confidentiality, and an advertisement by professional and advertising rules. A front desk handles walk-ins, emergencies and appointments in the same hour.
  • In education, the calendar is the year: admissions, terms, examinations and results come in waves, and the people involved include students, parents and teachers, each with different needs.
  • In infrastructure and real estate, work runs over months or years, across many contractors and approvals, and a delay in one place moves everything after it.
  • In defence and aerospace, security, documentation and traceability are not features; they are the starting conditions.
  • In energy and sustainability, the work spans field sites, equipment that must be maintained, and reporting that has to stand up to scrutiny.
  • In technology and IT, and in enterprises generally, the challenge is often fitting into systems and processes that are already there, rather than replacing them.

A generic system treats these conditions as edge cases to be configured later. An industry-native one treats them as the design brief.

What industry-native means in practice

For us it comes down to four habits.

1. Understand the work before designing the system. We spend time with the people who do the job: the receptionist, the site engineer, the coordinator, the owner. What do they do at 9 am? What goes wrong on a busy day? What do they work around? The answers usually change the design.

2. Build the rules in, not on. Every industry has its own regulations, standards and unwritten norms. Where a rule is clear, the system should help people follow it as part of the normal flow of work, not leave it to a checklist after the fact.

3. Use the industry’s own words. A system that calls a patient a “customer” or a site a “project instance” makes people translate in their heads all day. Plain language, in the terms the industry already uses, makes a system easier to trust and quicker to learn.

4. Keep people in charge of decisions that matter. Automation should take the repetitive work off people’s hands. Decisions with consequences, such as what is said publicly in a business’s name, should stay with a person. We have written more about this in People stay in charge.

Why it matters

The cost of a poor fit rarely shows up in the purchase price. It shows up later:

  • as staff keeping a parallel spreadsheet because the system does not match how they work;
  • as mistakes that a system aware of the industry’s rules would have caught;
  • as long training periods, because the system speaks a language nobody in the business uses;
  • as a tool that is quietly abandoned a year after it was bought.

A system shaped around the real work is used, and a system that is used is the only kind that can make a measurable difference.

The industries we work across

SMRIT LABZ works across healthcare; pharmaceuticals and diagnostics; human capital; real estate and infrastructure; defence and aerospace; energy and sustainability; education; technology and IT; and enterprise. The range is deliberate. Patterns learned in one industry, such as approval routines in healthcare or scheduling in education, often help in another, as long as the starting point is always the real conditions of the industry in front of us.

An example: our first product

Our first product, Baila Lento, is a digital marketing platform for growing businesses and agencies. It was shaped by this approach. Local businesses told us they wanted help keeping their social media and Google listings active, but they were not willing to let anything go out in their name without seeing it first. Healthcare clients added another condition: their posts must follow the rules for healthcare advertising. So approval and industry rules are part of how the product works, not settings added later. We describe how we built it in Why our first product is a marketing platform.

If your organisation has an operating challenge that generic tools have not solved, we would like to hear about it. Write to us at connect@smritlabz.com.

More insights