Out of the spreadsheet, without replacing what already works.
When work runs on spreadsheets, email threads and a handful of SaaS logins, your people become the integration layer. We build internal tools and client portals on Laravel, like the one our own clients use, on top of the systems you already run. Then we keep them running.
Who this is for, and who it is not.
A good fit if
- Orders, approvals or requests live in shared spreadsheets, and nobody is sure which copy is current.
- Clients, partners or suppliers email you for status updates that already exist somewhere in your systems.
- Staff re-key the same data between your ERP, accounting package, CRM or WooCommerce store every day.
- A SaaS tool covers most of the process, and the rest lives in workarounds that keep growing.
Probably not the right call if
- Your process fits a standard SaaS product well. Pay the subscription; it will cost less than a build.
- You want to replace your ERP or accounting system outright. That is a different project, and rarely a good one.
- The process changes every week and nobody owns it. Software will freeze the confusion rather than fix it.
What changes for your team.
One current version of every record
Staff, clients and suppliers look at the same record. Status questions stop arriving by email and phone, because the answer is already on the screen.
Data entered once
Changes reach the ERP, accounting package and CRM through integrations, instead of being retyped by someone at the end of the day.
A record of who did what
Every approval, edit and upload is tied to a named user and a time. Disputes and audits are answered from the system, not from memory.
The parts that make it hold up in production.
Roles and permissions
Staff, clients, partners and suppliers each get their own accounts and see only what they should. Permissions are enforced on the server, down to individual records where needed.
Integrations with what you run
Connections to your ERP, accounting package, CRM, WooCommerce store or existing database through APIs, webhooks or scheduled syncs. Failed syncs retry on a queue and show up in the admin instead of vanishing.
Audit trail
A log of changes, approvals and sign-ins, each tied to a user and a timestamp. You can see who changed what, and when, without anyone digging through server logs.
Documents and file handling
Uploads, generated PDFs and document history, kept in private storage and served through expiring links. Files follow the same permissions as the records they belong to.
Reporting and exports
Dashboards and filters built around the decisions your team actually makes. CSV and Excel exports for the people who will always want a spreadsheet.
Single sign-on where needed
Staff sign in with their Microsoft or Google accounts over OpenID Connect, or SAML where your identity provider requires it. External users get their own login with two-factor authentication.
A layer on top of what you already run.
The platform owns the workflow, the permissions and the audit trail. Your existing systems stay the source of truth for the data they already hold.
-
Where people use it L4Staff back-office Client portal Supplier portal Admin panel
-
What the platform handles L3Roles & permissions Approvals Audit log Files & PDFs Reports & exports
-
How it connects L2REST APIs Webhooks Scheduled syncs Queued retries SSO
-
What you already run L1ERP Accounting CRM WooCommerce Existing database
From first call to running in production.
Each step ends in something you can look at. Scope grows after something is live, not before.
-
01
Map the real process
We trace each step, spreadsheet and handover with the people who do the work. The output is a data model, a role matrix and the list of systems we must connect to.
-
02
Prove the integrations first
We connect to your ERP, accounting package or CRM before building screens, because that is where the surprises are. Rate limits, missing fields and dirty data get found early, not at launch.
-
03
Design and build together
Screens are designed in Figma by the engineers who build them, then shipped in increments to staging. Your team works through real flows long before anything goes live.
-
04
Roll out, then run it
We launch to one team or one group of clients first, and widen access once the edge cases are handled. After launch we stay on it: backups, monitoring, upgrades and the next change.
Published prices, fixed before we start.
€1,000
delivered within a week
We read the system you already have and tell you what is actually wrong with it, what it would take to fix, and what it would cost.
€5,000 – €20,000
typical project
Fixed scope, fixed price, agreed before anyone writes code. Most of what we do sits in this band.
from €750
per month
We take the system over and keep it alive. This is the part most people discover they needed about six months after launch.
What moves the price for Custom Platforms & Portals
- How many systems we integrate with, and how usable their APIs are; a documented API costs far less than a database with no interface.
- How many distinct types of user there are, and how fine-grained their permissions need to be.
- Whether existing data has to be migrated and cleaned before launch, rather than starting fresh.
- Requirements beyond standard logins and exports, such as SSO, document generation or detailed audit reporting.
What we work with
Questions we get asked.
No, and we would advise against it. The platform sits on top of what you already run and reads and writes through its APIs, so the ERP stays the system of record for stock, invoices and ledgers. If a system has no usable interface, we tell you before we quote and work out the least risky way around it.
If one fits your process, buy it. A build makes sense when the process is what sets you apart, when several tools are held together with spreadsheets, or when clients and suppliers need access that per-seat pricing makes awkward. We will tell you which case you are in before we quote.
In your own infrastructure accounts, with the repository in your organisation from the first commit. Access is enforced by roles on the server, files sit in private storage behind expiring links, and sensitive actions are logged. The code is yours as it is paid for, so you can take it elsewhere at any point.
We keep running it on a monthly plan: backups, monitoring, security patches, framework upgrades and a budget of hours for small changes. Integrations are what break when a vendor changes an API, so failed syncs alert us rather than waiting for someone to notice a missing order.
Yes, where they earn their place. Typical additions are drafting replies to client requests, extracting fields from uploaded invoices or contracts, and searching across the documents in the portal. They come after the core workflow works, and they respect the same permissions as everything else.
