When the standard platform is not quite the answer
Most requirements that sound like custom development turn out to be configuration. With 47 modules, 12 permission profiles, a universal workflow engine and a rules engine that reaches every module, the platform absorbs more than most buyers expect. Some requirements genuinely are not configuration. This page is about telling the two apart before anyone quotes anything.
Configuration or development?
The line matters. One is included in your rollout and takes days. The other is a scoped project with a quote attached.
Already in the platform
Done in the admin screens, by your team or ours, without engineering time.
- Asset hierarchies across 10 object types and 38+ dispositions
- 12 role and permission profiles, cloneable between users
- Multi-tenant separation, with license administration per tenant
- 2FA and SSO: TOTP, email OTP, WebAuthn, LDAP-AD, SAML 2.0, Azure AD, Google Workspace
- Notification rules from any module, with escalation, cooldown and acknowledge/snooze/resolve
- Six delivery channels: email, WhatsApp, SMS, push, in-app SSE, webhook
- Industry-tagged alert templates, plus a simulator that fires through the real dispatcher
- Approval workflows that gate any process, including delegation
- Digital signature with PIN tokens and chained SHA-256 audit
- Per-reader auto-processing rules and reader-triggered actions
- Outbound webhooks to your ERP with OAuth2 or API-key
- Three interface languages: English, Portuguese, Spanish
Scoped as a separate project
Requires engineering time. Quoted, scheduled and delivered against a written spec.
- Business logic specific to your process, beyond rule configuration
- Regulatory reports with a mandated layout not covered by Smart Reports
- Screens built around a workflow unique to your operation
- Data migration from a legacy system with non-standard structure
- Support for a device family outside the nine identification technologies
- Inbound integration patterns beyond HTTP, MQTT and direct SQL
How a request runs
No surprises in the invoice. You see the scope and the cost before work starts.
Describe it
Tell us the outcome, not the feature. “Auditors need proof of every temperature excursion” opens more options than “add a column to the report”.
We check the platform first
Often the capability already exists, or configuration covers it. When that is the case we say so — it is faster for you and cheaper for us to support.
Scope and quote
If it is genuinely development, you get a written specification, a timeline and a price before anyone starts building.
Build and hand over
Delivered against the specification, with documentation and, where it makes sense, folded into the standard product so it stays supported.
Before you ask for custom
Three places worth looking first. Many requirements are already covered.
Platform features
The full capability list, module by module. More is in there than most rollouts switch on.
Integrations & API
Over 1,000 documented endpoints. If the requirement is “this data needs to be somewhere else”, it is an integration, not a build.
Platform modules
47 modules across eight families. More capability ships switched off than most rollouts ever turn on.
Describe the requirement and we will tell you which it is
Send the outcome you need. We will come back with whether it is configuration, integration or development — and we will tell you honestly when it is the cheap one.
