Smart Info Technologies

Adaptive business software

Custom-fit software without the custom-software trap.

Most companies are forced to choose. Buy a package and reshape the operation around the software. Or build something custom that fits today, then pay for every change tomorrow.

Smart Info Technologies is built to break that trade-off. We shape the system around your processes, terminology, rules, roles and integrations — while keeping what is specific to you separate from the platform we continue to improve.

Software that fits how you work. And keeps fitting.

Operating since 2007 · Framework in production since 2014 · Current generation shipped in 2026

A shipment record with five tabs, dozens of fields, and editable stops and legs grids
Built around the operation, not a fixed templateFive tabs, dozens of fields, editable grids and multi-modal routing can be shaped around the work. Underneath, the framework runs the structured business description directly rather than maintaining a separate hand-built screen.
2007Operating continuously since
2014Framework in production since
MillionsShipments planned & executed
2026Current-generation platform

The trade-off we eliminate

Built around your business. Built to change with it.

You should not have to choose between software that fits the operation and software that can keep evolving. The point of our architecture is to give you both.

FIT

Fit the operation

Your terminology, workflows, rules, customer requirements, roles and exceptions belong in the system — not in a spreadsheet sitting beside it.

CHANGE

Change without another project

When a process, role, rule or partner requirement changes, supported changes are made to the business description rather than starting another custom development cycle.

STAY CURRENT

Keep moving forward

What is specific to you stays separate from the shared platform underneath. We can keep improving the platform without turning your fit into a frozen custom version.

What ships on day one

Built in, not bolted on.

Every application starts with the parts that usually take a project its first six months.

Role-based security

Who can see and do what is part of the description, and the system enforces it on every single request.

Federated identity

Sign-in runs on Google Firebase. We hold no passwords. MFA available.

Tenant data isolation

Each organisation's data is kept separate by the framework itself, not by everyone remembering to be careful.

Web, mobile, desktop

One description, all three. Nothing is built separately for mobile, so nothing can fall behind.

Grids that do the analysis

Multi-column sorting and grouping handle most day-to-day analysis without exporting anything.

Charts from grouped data

Pie, bar and line views of any grouping, drawn from the same screen definition.

Advanced search

Complex criteria with AND / OR conditions, on any entity, without a report request.

Integration mapping

Define mappings to trade data with the outside world over EDI, XML and API.

The framework in detail

Answers without a report request

Your team can do the analysis themselves.

In most systems, "group these shipments by mode and show me the revenue split" is a request that goes to IT and comes back next week as a report. Here it is something a dispatcher does in the grid, in about four seconds, on any column.

Group by anything. The totals calculate themselves. Turn on the chart and it draws from whatever grouping is on screen, switching between count, revenue, cost and margin as you click. Nobody configured this view, and no developer was involved in making it exist — it comes with every screen on the framework, on every field, for free.

Shipment search grid grouped by mode with running totals, alongside a donut chart of revenue by mode
Grouped in the grid, charted on the spotShipments grouped by mode with revenue and cost totalled per group, and the same grouping drawn as a chart. Sample data.

See more screens from the definition

Avoiding the custom-version dead end

Built around you. Never frozen in time.

The real question is not whether software can be configured. It is what happens after it has been configured heavily. Does every future improvement threaten what was built for you?

We keep the shared platform and your operating model separate. Your fields, wording, screens, rules, roles and partner connections live in their own layer over the common foundation. That is what lets the system fit deeply without requiring a separate customer fork.

01 / PLATFORM

The shared foundation

The foundation every customer starts from and the part we keep improving. We are not maintaining a separate product branch for every account.

02 / YOUR OPERATION

What is specific to you

Your fields, terminology, screens, rules, customer requirements and partner connections. They can be shaped around the operation without being carved into the common platform.

03 / EACH ROLE

The right operating view

A dispatcher, manager and controller can use the same system with different working views and permissions. Access is enforced by the platform, not merely hidden in the interface.

Configured heavily. Upgraded anyway. The business value is simple: fit today should not become technical debt tomorrow.

The technical detail — base objects, customer layers, role layers and the boundaries of the model — is documented on the How it works page.

Built for the AI era

AI is getting smarter. The business still needs rules.

AI can understand requirements, interpret documents, propose changes and increasingly take action across workflows. That makes a second question more important: what is the AI actually allowed to do?

A real operation has customers, orders, approvals, calculations, exceptions, permissions and connections to other systems. Those boundaries cannot live only in a prompt. Our framework already represents much of that operating model in a structured form and enforces it when the system runs.

AI can help withThe operating model governs
RequirementsInterpret conversations and documentsWhich business objects, fields and rules are valid
ChangePropose definitions, mappings and testsWhat structure is accepted and what must be approved
OperationsRecommend or automate workRoles, permissions, approvals and allowed actions
IntegrationUnderstand partner formatsKnown mappings, contracts and system boundaries
AccountabilityAccelerate people and processesDeterministic execution and the system of record

AI understands intent. Your business model defines the boundaries. The framework executes them.

Today we use AI where it earns its place — helping draft definitions from requirements, mapping partner formats, creating test data and documentation, and supporting analysis over structured operational data. We do not need probabilistic AI to decide whether a core permission, business rule or financial calculation is valid.

AI-generated software can also be useful. Our distinction is not that code cannot be tested or governed; it can. The point is that faster code creation does not make the production lifecycle disappear. SIT reduces how much application-specific code has to exist in the first place.

How we work

Work directly with the people who built the platform.

Complex operational software changes faster when the business problem is not filtered through layers of account management. The team responsible for the platform stays close to the people using it.

Proven and current
Smart Info Technologies has operated continuously since 2007. The framework has run production systems since 2014, and the current generation shipped in 2026 after more than a decade of production experience.
Senior access
The people who understand the architecture are involved in the system and the customer problem. There is no tier-one script between an operational issue and someone who can change the platform.
Continuity
Source code and configuration escrow are available on request. For larger engagements, customer-managed configuration and hosting can be part of the commercial model.
Infrastructure & assurance
Applications run on Google Cloud Platform with SOC 2-aligned controls, federated identity, tenant isolation and published technical security detail for your review.

The person you explain the problem to stays close to the person who can change the system.

Proof

Proven approach. Current platform.

The architecture has been running production operations since 2014. The current generation shipped in 2026. These products show the same platform supporting very different operating models.

SmartSCM — Transportation management

Our own SaaS TMS for freight brokers, forwarders, 3PLs, agency networks and shippers. Order to financial settlement in one system, with EDI, XML and API links to every trading partner. smartscm.com →

Sports equipment lifecycle management

Three configured variants of an equipment tracking, inspection and certification platform for a single customer — same framework, three different operating models.

RFID vendor-managed inventory

An RFID-driven VMI platform where tag reads at the point of use drive replenishment, usage reporting and billing.

Customer names available under NDA. In every case the customer owns their process, configuration, data and custom development; SIT owns the framework.

As a small company competing in a land of giants, our value proposition depended on working smarter. This required an IT partner that could share our vision and deliver to our requirements. SmartSCM has done that since 2012.
Theodore PrinceChief Strategy Officer and Co-founder, Tiger Cool Express LLC
SmartSCM is not an ordinary TMS. It is a one of a kind, ever evolving program customised to our unique business model — managing multiple modes of transportation and warehouse distribution in one place. It has been essential to our success since 2009.
Shawn GotschallOwner, RE Transportation, Inc.

Security

Written for your IT team, not around them.

We publish the technical detail up front and can support vendor security reviews as the conversation progresses. Where a control belongs to Google rather than to us, we say so.

  • No passwords stored — identity is federated through Google Firebase
  • Every API request carries a short-lived signed token, verified server-side before it reaches application code
  • TLS 1.3 in transit, with older TLS versions disabled
  • AES-256 encryption at rest on Google Cloud Platform, keys managed and rotated by Google Cloud KMS
  • Tenant data isolation and role-based access enforced by the framework
  • SOC 2-aligned controls; multi-factor authentication available per tenant
  • High-availability database with recovery procedures designed to restore service in minutes

Bring us the process your current software can't handle.

A workflow, exception, customer requirement or integration that forces workarounds today. That is a better starting point than a generic feature tour.