01
Sales
Qualify
Customer, requirement, timing and commercial owner are recorded.
Industry · SMEs & operations
Operational software for businesses that have outgrown the spreadsheet—but not their judgement.
Thalenor builds focused internal tools, dashboards, workflow systems and automation for smaller businesses whose distinctive processes no longer fit generic software cleanly.
WORKFLOW · OWNERSHIP · EXCEPTION06
A clear answer
What does Thalenor build for SME and operations organisations?
SMEs often reach an awkward middle: the business is too complex for shared spreadsheets and messaging, but a large enterprise platform is expensive, rigid or disproportionate. Thalenor helps map the operation, retain useful existing tools and build the missing layer—an approval workflow, order system, field application, customer portal, reporting service or connected operational workspace.
Operating landscape
One connected operation. Six places where context can break.
The system should carry meaning across these hand-offs, not leave users to rebuild it in messages and spreadsheets.
01
Enquiry and quotation
Qualification, ownership, pricing inputs, approvals, document creation and follow-up.
02
Orders and jobs
A shared record of what was promised, current state, dependencies, exceptions and accountable next action.
03
Inventory and purchasing
Requests, approval, supplier orders, receipt, adjustments and visibility appropriate to each role.
04
Field and service work
Scheduling, mobile job information, checklists, evidence, signatures, expenses and customer updates.
05
Approvals and documents
Clear thresholds, delegates, reminders, versioned outputs and a traceable decision history.
06
Reporting and management
Operational definitions, exception queues and scheduled summaries built from source records rather than manual consolidation.
Workflow in view
A credible product should make the work visible before it tries to make it fast.
Follow the record, the responsible role and the decision that must remain human.
ILLUSTRATIVE MODEL · FICTIONAL RECORDS
A quotation becomes an order without being retyped across four tools.
The system connects commercial approval to fulfilment while keeping exceptions visible.
QUOTATION → APPROVAL → FULFILMENT
ILLUSTRATIVE OPERATING MODEL · 06 STATES02
Pricing rules
Price
Standard items calculate automatically; exceptions request approval.
03
Approver
Approve
The decision shows margin, terms and reason—not a detached message.
04
Order system
Confirm
The accepted quotation creates the order once.
05
Operations
Fulfil
Stock or production states update against that same order.
06
Management
Report
Commercial and operations views use the same source record.
Illustrative workflow. The right first loop depends on the business’s volume, risk and existing tools.
Where design judgement matters
The hard part is rarely the screen someone asks for first.
01
The problem is rarely the spreadsheet itself. It is shared operational state without ownership.
Spreadsheets remain excellent for analysis and flexible planning. They become fragile when many people use cells as a workflow, permissions are broad and no one can tell which update changed the outcome.
- AKeep analysis in spreadsheets where it works
- BMove shared states and approvals into controlled records
- CPreserve import and export for practical ownership
- DReplace one critical workflow before chasing a full ERP
02
An approval should explain what changed and why this person is deciding.
Email and chat approvals lose the object, threshold and final state. A useful system carries the relevant context, applies the right rule and records the decision without making routine work bureaucratic.
- ADefine thresholds and delegates
- BPresent the decision context, not every field
- CPrevent duplicate or stale approval actions
- DEscalate only when time or value warrants it
03
A dashboard cannot repair undefined operational language.
Before charting orders, leads or delays, teams must agree what each state means and when it changes. Otherwise the dashboard makes inconsistent data look authoritative.
- ADefine states with entry and exit rules
- BShow exceptions alongside totals
- CLink measures back to source records
- DSchedule decisions, not just reports
04
Adoption is a product constraint.
A system can be technically correct and still fail because it adds steps, ignores the shop floor or removes a workaround before replacing its purpose. The release plan must include the people doing the work.
- AObserve real users before finalising flow
- BPilot with a contained team or process
- CImport only useful historical data
- DKeep support close during changeover
Decision guide
When should an SME replace spreadsheets with custom software?
The answer is not ‘when a spreadsheet is large’. It is when operational risk and repeated coordination justify a controlled shared system.
Custom software becomes reasonable when one important workflow has stable rules, repeated volume, several owners and a measurable cost of coordination or error.
01
Look for simultaneous ownership
If several roles change the same operational record and need different permissions, a spreadsheet is carrying application responsibilities.
02
Count reconciliation, not rows
The cost often appears in repeated checking between sales, stock, accounts and delivery—not in file size.
03
Identify the distinctive workflow
Buy software for standard functions. Build only the process that creates advantage or cannot fit responsibly.
04
Define the smallest complete loop
A quotation-to-order flow or purchase approval may create value alone; partial fragments often create more copying.
05
Price the changeover
Data cleanup, training, parallel operation and support are part of the investment.
06
Protect reversibility
Exports, documented rules and client-controlled access make future change possible.
Relevant capabilities
The engineering disciplines this work usually touches.
Boundaries built into the product
Responsible software states what it will not decide.
A disclaimer cannot compensate for a workflow that hides uncertainty or lets sensitive actions happen without ownership.
01
Proportionate scope
A focused workflow can be more valuable than a premature all-in-one business system.
02
Source ownership
Client-controlled exports, repositories and accounts reduce avoidable dependency.
03
Operational override
Authorised people need a safe way to correct exceptional states with a reason and audit trail.
04
Offline reality
Field, factory and warehouse environments may require cached data, queued work and simple interfaces.
05
Automation visibility
Staff should see what the system changed, what failed and what still needs a person.
Practical questions about SME and operations software.
It can be when the first scope is narrow and solves a recurring, costly workflow. A large all-in-one platform is usually the wrong place to begin.
Replace one fragile operating loop with a dependable one.
Show us where information is copied, chased, approved or corrected today. We will help choose the smallest system that changes the work.