Logo, Mikro, SAP, Netsis, Uyumsoft — your ERP keeps the system of record. But what about leave, approvals, expenses, maintenance, field work, asset assignments and reporting? Those still live in Excel, WhatsApp and email. The Intranet Portal sits on top of your ERP, leaves it as the single source of truth, and digitalises every remaining process through a monthly subscription. No setup fee, no licence, no per-user charge.
The Intranet Portal doesn't replace your existing ERP; it works alongside and on top of it. The ERP remains the single source of truth; the portal reads data from the ERP, writes approved outputs back to it, and gives your employees a modern interface for the hundreds of internal processes the ERP never touches (leave, approvals, expenses, tickets, asset assignments, maintenance, field work, announcements). You get all of this through a single monthly subscription — with no man-day setup fee, no software licence and no per-user charge. You request new modules as you need them; there's no surprise project invoice. Capital expenditure is zero; you carry a single, predictable operating cost.
Employees served on a single portal (group scale)
Live portal projects in production
Proven, ready-to-use business process modules
ERPs integrated with (Logo, Mikro, SAP, Uyumsoft, Oracle)
Business processes left unsolved by the high cost of ERP customisation — still running in Excel, WhatsApp and email — and how the portal solves them.
Leave, advance and expense requests still circulate in Excel files and WhatsApp messages. Who approved it, which stage it's at, when it was paid — no one knows for certain.
SolutionSelf-service requests and a central approval engine: employees raise requests from mobile or web, the approval chain runs automatically, and every step is recorded. The approved result is transferred cleanly into ERP payroll/accounting. Your ERP doesn't solve this because customising the same hierarchical approval chain for every document type is a prohibitive cost.
Invoice payment decisions are made in email traffic between Finance and Procurement. Duplicate payments, missed due dates and monthly budget overruns are only spotted once it's too late.
SolutionInvoice tracking and payment-order module: it pulls e-invoices from the ERP, catches duplicate payments, shows the monthly payment budget live, runs the Finance→Procurement→MD approval chain and generates the bank instruction. The ERP holds the invoice but can't model this multi-party payment-planning flow; customising it is the most expensive item of all.
Cross-departmental requests (IT, admin, quality, technical) get lost in email. Who it's assigned to, when it will be resolved, what its history is — none of it can be tracked.
SolutionCross-departmental ticketing and help desk: category-based routing, assignment, SLA status, activity history and reopening. Every request has an audit trail. The ERP has no concept of a department-to-department work-request lifecycle — this is an ITSM need entirely outside ERP scope.
Who holds which laptop, vehicle or piece of equipment is tracked in Excel. Stock counts mean walking the site item by item, and handovers go unsigned.
SolutionAsset assignment and management: employee assignment acknowledgement, staff-to-staff transfer, QR-based location counting. The ERP's fixed-asset ledger tracks depreciation but doesn't hold 'who is physically holding the laptop today', the signed handover or the QR count.
Attendance for field and multi-shift teams is recorded on paper timesheets or keyed into Excel by hand. The same data is entered twice — once on site and again in payroll — and errors carry through to payroll.
SolutionTime & attendance: QR + GPS geofenced mobile clock-in/out, shift and rotation planning, an exception queue, manager approval, and a monthly timesheet that is locked and transferred to payroll. ERPs have no native QR+GPS geofenced mobile clock-in or shift rotation; on SAP/Logo it's an expensive customisation project.
Announcements, menus, shuttle times and HR documents are scattered across different places. Employees have to call someone to find information, and read-receipts are never captured.
SolutionCorporate communications and employee services: read-tracked announcements, a news feed, the canteen menu, shuttle routes, the employee handbook and surveys. This is pure employee-experience content; it belongs to no ERP's domain, and Logo/SAP would never host it.
Equipment faults are reported by phone and work orders run on paper. Which fault was resolved when, what materials were consumed, what the MTTR is — none of it can be reported.
SolutionMaintenance management: a fault→work-order→closure state machine, technician assignment, material consumption on the work order (deducted automatically from stock), automatic work orders from the preventive-maintenance schedule, and MTTR reports. This CMMS flow is either the expensive SAP PM module or a separate system that never connects to the ERP at all.
Managers raise a report request with IT to see ERP data and then wait days. No one can produce a single view across modules (tickets + approvals + expenses + field work).
SolutionRole-based dashboards and reporting: it blends the portal's own data (tickets, approvals, asset assignments, requests) with ERP data into role-appropriate dashboards, with an optional AI assistant you query in natural language. On its own the ERP only reports its own financial/logistics figures; it can't produce cross-module KPIs.
Own it with no man-day, licence, per-user, maintenance or server cost.
Conventional ERP customisation and enterprise software projects begin with a consultancy invoice running to tens or hundreds of man-days. With the Intranet Portal there is no setup fee. The day your subscription starts, the portal is live; your first modules are already in place, tailored to your organisational structure.
You don't buy a software licence paid upfront that takes years to amortise. There is no one-off, large capex item. You don't buy the software; you subscribe to the service. Your budget isn't locked in by a major investment from day one.
A 5,000-employee group and a 50-person company use it on exactly the same basis: you pay no per-user fee. Adding the worker on site, the specialist in the office or the managing director to the portal doesn't increase your cost. Adding a new user never means buying a new licence.
You don't buy a separate annual maintenance agreement, a version-upgrade invoice or a support package. Maintenance, upgrades, security patches and improvements are all included in the subscription. The system stays continuously up to date, and you pay nothing extra for it.
You don't need to buy servers, rent a data centre or manage hosting. Hosting, backups, scaling and infrastructure operations are our responsibility and are included in the subscription. Your IT team focuses on the business, not the infrastructure.
All of these items are consolidated into one monthly subscription fee. There are no hidden costs, no year-end surprises and no 'add-on module price list'. You plan your budget with confidence: you know exactly what you'll pay each month from the outset. Zero capex, a single opex line.
When you want to digitalise a new process, you don't have to launch a project tender from scratch. You request new modules and features within the scope of your subscription, on reasonable and transparent terms. The scope is deliberately open-ended; as your business grows, the portal grows with it, with no surprise capex invoice.
The portal doesn't replace your ERP; it feeds it and is fed by it. Invoices, accounts, stock and payroll stay in the ERP; approvals, processes, field work and self-service live in the portal. The portal reads from the ERP and writes the approved result back to it. The risk of duplicate records, data fragmentation and 'which one is correct' chaos disappears.
Instead of ERP customisation projects that drag on for months, you go live quickly on a proven module foundation. Core modules such as the approval engine, self-service, expenses, tickets and announcements are ready to go and are adapted to your processes. Within weeks your employees start using the portal.
The portal is deliberately open to expansion, but that means reassurance, not uncertainty. New requirements are added on reasonable, transparent, pre-agreed terms. You start with modules a software house genuinely runs in production (HR, time and attendance, approvals, expenses, maintenance, field work, procurement, CRM); the scope expands as you grow.
Every one comes from a live project. Each module will soon get its own detail page.
A single polymorphic approval engine that plugs into every document type (leave, advances, expenses, invoices, payments, requests, bookings). Dynamic routing by amount band, hierarchical/parallel chains, delegation, SLA escalation and step-level authorisation. One live 'Pending Approvals' inbox spans every module.
ERP gap: ERPs have no single, reusable approval matrix that is document-agnostic, delegation-aware and routed by amount band; customising each document separately is a prohibitive cost.
Employee self-service built on a read-only mirror of the ERP (SAP/Uyumsoft): personal profile, payslip viewing, personnel documents, org chart, and an HR analytics dashboard (demographics, turnover, attendance, OHS). Non-ERP companies are managed via Excel import.
ERP gap: The ERP is the master source for payroll/personnel data but offers employees no self-service face; the ERP won't provide the bridge layer that opens personnel data — minimised for data-protection — to 5,000 people.
QR + GPS geofenced mobile clock-in/out, shift definitions and rotation planning, an exception/anomaly queue, manual-entry and overtime requests, manager approval, and a monthly timesheet that is locked and transferred to payroll.
ERP gap: Standard ERPs have no native QR+GPS geofenced mobile punch, shift rotation or approval flow for field staff; building it on SAP/Logo is an expensive bespoke project.
Appraisal cycles, competency and objective catalogues, configurable calculation formulas, multi-step approval chains, self/manager/reviewer appraisal flows, and PDF scorecards.
ERP gap: Objective setting, competency scoring and 360 approval chains sit outside ERP scope; the ERP add-ons that offer them are expensive licences and can't express company-specific weighting formulas.
Position-based training matrix, training programmes, question bank, timed online exams (mock runs/scoring), automatically generated verifiable certificates, and team/individual compliance tracking.
ERP gap: The ERP can record that training took place but can't deliver online exams, enforce a position-mandatory training matrix, or issue and verify certificates; a separate LMS licence is required.
Receipt-based expense entry (mobile photo + OCR), categorised expense reports, approve/reject flow, paid/offset status, advance reconciliation, and role-based income-expenditure / budget-versus-actual dashboards. Approved totals transfer cleanly into finance.
ERP gap: The ERP holds the final accounting entry but doesn't offer the employee-centric submit-receipt-approve-pay lifecycle or the budget-versus-actual self-service dashboards.
A request→order→goods-receipt flow, amount-based multi-step internal approval, three-way invoice matching, an e-invoice inbox, and tendering/RFQ opened to external suppliers: bid collection, side-by-side comparison, weighted scoring and tender award.
ERP gap: The ERP holds the order/invoice but the amount-banded internal approval, three-way matching and competitive multi-stage tender object are either absent or tied to an expensive upper tier such as SAP MM; most companies run this in Excel and email.
Pulls e-invoice/tax-authority status from the ERP, calculates the net amount payable after advance/refund offsets, catches duplicate payments, keeps a deferral history, shows the monthly payment budget live, and generates the bank instruction from an MD-approved payment list.
ERP gap: The ERP holds the invoice but can't model the multi-party pay/defer negotiation between Finance, Procurement and the MD, the live budget ceiling and the duplicate-payment protection; customising it is extremely costly.
A full ticketing system for cross-departmental work/quality/IT requests and customer support: category-based routing, assignment/reassignment, an open/resolve/close/reopen state machine, internal-note separation, SLA status and an activity trail.
ERP gap: The department-to-department work-request and customer-support lifecycle is an ITSM/help-desk need outside ERP scope; the ERP has no such concept.
Tracking of assets assigned to staff, employee assignment acknowledgement, a staff-to-staff transfer/return flow (routed through the approval engine), a company-wide read-only inventory and QR-based location counting.
ERP gap: The ERP's fixed-asset ledger tracks depreciation but doesn't hold who is physically holding the laptop today, the signed handover, the staff-to-staff transfer or the QR count.
Equipment cards, a fault→work-order→closure state machine, technician assignment, material/labour on the work order with automatic consumption from stock, automatic work-order generation from the preventive-maintenance schedule, and MTTR and fault-frequency reports.
ERP gap: The equipment-based fault→work-order cycle, the preventive-maintenance calendar and technician field execution don't exist in the ERP; a CMMS is either the expensive SAP PM or a separate system that doesn't connect to the ERP.
Vehicle inventory; inspection/insurance/toll/tyre expiry alerts, fuel and expense logging, driver assignment, traffic fines, a vehicle booking/approval flow, cost analysis, and live GPS/CAN bus telematics integration.
ERP gap: The ERP sees a vehicle only as a fixed asset; there's no inspection alert, booking flow or live telematics, so real fleet operations always require a separate system.
An alarm→work-order→completion→invoicing cycle; a live operations panel (map + drag-and-drop assignment), geofenced technician presence checks, SLA countdown, barcode-based part fit/removal, photo evidence and a signed PDF closure report.
ERP gap: The ERP can't verify field staff's real-time geographic presence against a work order; field-specific SLA timers, mobile acceptance and real-time assignment fall outside ERP architecture.
Conflict-checked meeting-room/resource booking, meeting planning with attendee and document management, front-desk visitor registration, and a reception dashboard with appointments and check-in/check-out.
ERP gap: Resource scheduling, conflict detection and front-desk visitor entry/exit are facility-operations matters; the ERP models neither physical resource availability nor visitor registration.
Read-tracked announcements, an internal news/blog, surveys, the canteen menu, shuttle routes, the employee handbook, a corporate calendar, an exchange-rate display, and a partner-firm / employee-discount directory. The content layer that makes the portal a daily home page.
ERP gap: Read-tracked announcements, a news feed, the canteen menu, shuttle times and a discount directory are pure intranet/employee-experience functions; the ERP has no equivalent whatsoever.
Kanban task/project boards (assignment, attachments, overdue notifications), a folder-based file manager and a categorised/tagged corporate document library with search and public/private sharing. An idea/suggestion pool gathers bottom-up improvements.
ERP gap: Team task boards (Trello/Jira territory), a searchable corporate DMS and a suggestion pool are productivity areas the ERP doesn't occupy; they'd otherwise require a separate SharePoint/PM subscription.
Tell us the process. If it’s not here yet, we scope it as a new module within your subscription — no surprise project invoice.
Book a Demo →The portal reads master data from your ERP and writes approved results back. Deepest, proven track record: Uyumsoft.
UyumApi REST and direct Oracle database — personnel mirror, e-invoice and approval write-back, proven in production.
Tiger, GO and Logo Objects via REST/service and SQL database — personnel, cost centres, e-invoice, accounts.
Mikro Fly / Jump via direct SQL and web service — personnel, accounts, stock and cost-centre sync.
Business One and S/4HANA via OData, Service Layer and BAPI/RFC — enterprise, multi-company.
Logo Netsis via NetOpenX REST API and SQL — personnel, accounts, cost centres and e-invoice.
Any ERP with an API or accessible database is an integration candidate — vendor-agnostic. Book a demo and we’ll scope it.
Book a Demo →The portal connects to your existing ERP (Logo, Mikro, SAP, Netsis, Uyumsoft, Oracle) through a secure integration layer. It mirrors master data such as personnel, accounts, invoices and stock read-only; the ERP remains the single source of truth. You don't have to migrate any data.
We select the modules you need (approvals, leave, expenses, time and attendance, ticketing, maintenance, field work, procurement...) from a proven foundation and adapt them to your organisational structure. Roles, departments and approval chains are defined to match your organisation. You go live within weeks.
Everyone from the worker on site to the managing director logs into a single portal: no per-user licence. Requests are raised, approvals flow, and real-time notifications arrive. Approved results (timesheets, expense totals, payments) are written cleanly back to the ERP; double data entry ends.
When a new process needs digitalising, you don't launch a project tender from scratch; you request the module within the scope of your subscription, on reasonable and transparent terms. Maintenance, upgrades and hosting are always included. No surprise capex — just a single, predictable monthly cost.
Book a 30-minute demo. Tell us which ERP you run and which processes are wearing you down — we’ll map your module plan together.
Book a Demo →