The applications your teams work in every day
Webshops, ERPs, portals, compliance platforms and the operational software a business runs on. Built to order because the off-the-shelf option did not fit, and still in production years later because someone has to be accountable for that.
Eight systems we built to order. Each one still in production.
Not a list of things we could build. This is the build log: what it is, who it runs for, and the one fact that proves it is real rather than a case study written after the fact.
ERP and CRM for speciality chemicals
For a US manufacturer, with our partner Farber Consulting Group
Quotes, orders, purchasing, inventory and warehouse, GHS chemical safety labelling, receivables, an in-house email engine, embedded Power BI, and a no-code automation builder the client's own staff use without calling us.
In continuous development since 2021, across 2,373 commits. It replaced the legacy desktop suite it grew out of.
Four ERPs, four countries, one database
For a European packaging group
Each country keeps the ERP it already runs on. Everything syncs one way into a single Azure SQL warehouse, and the group's Power BI, its B2B portals and its assistant layer all read from that one place instead of from four.
Five group companies, 300+ staff accounts, and one number that means the same thing in every country.
Six systems for one distributor
For Gumiimpex-GRP
Dispatch and delivery for the partner network, branch queueing, B2B ordering, a public fitment finder, a webshop, and the ERP middleware feeding all five. One client, one stack, six systems that know about each other.
The dispatch platform has run since 2022, through every twice-yearly changeover surge.
The European ERP connector practice
For mid-market groups across five ERP families
One shared connector core with a per-ERP sync service on top: WinTask, Datalab Pantheon, E-Line, a DATEV export for German accounting, and Netis. Each lands into the same BI platform, so adding a country is a deployment rather than a project.
Items resync every five minutes. The accounting sets run nightly, and retry themselves when a source is down.
Corporate document intelligence
For a corporate operations team
Azure Document Intelligence and Azure AI Search over contracts and invoices, with the validation rules and the human review step that make extracted data safe to act on rather than merely impressive in a demo.
95%+ extraction accuracy. Twenty hours a week of manual entry became two.
An assistant over a live catalogue
For a European distributor
A natural-language sales assistant that answers from the live product and stock database rather than from a scraped copy, behind a SQL safety gate, streaming its answer as it reads.
6,400 items in the catalogue, answered in the customer's own language.
A legal-data service at national scale
The backbone behind our own law-office platform
Statutes, consolidated laws and court decisions ingested continuously, stored so they can be searched in full text, and served to AI assistants over MCP with the source cited on every result.
Over half a million legal documents, kept current by eleven scheduled ingest jobs.
Service company CRM and ERP
Delivered for a North-American service business
Customer records, appointment scheduling, equipment history, quoting and accounting integration, delivered as one platform rather than as five subscriptions that do not talk to each other.
Delivered and handed over. Because the stack is standard Microsoft, the client's own team runs it.
NetSuite Sync and CapitalBridge started here
Both were built for one customer, both turned out to solve a problem that customer was not alone in having, and both are now products with their own roadmaps. That is the honest reason to hire a studio that also ships software: the second time we build something, it is not the first time.
One stack, deliberately
Opinionated stacks ship faster. And break less.
Every application we build runs on the same Microsoft-native stack we use for our own products. That is not a lack of imagination. It is what lets one team support a growing portfolio for years without the drift that kills long-lived software.
It is also the stack Microsoft itself runs on, which means long-term support, a serious security posture, and a hiring pool that is not limited to us.
.NET and Blazor
Server-rendered where that is right, WebAssembly where it is not. One language across the whole application.
Azure SQL and SQL Server
In your own subscription or on your own hardware. Blob storage for documents, Key Vault for secrets.
Hangfire, Service Bus, Functions
Background jobs and integrations that retry properly, because overnight is when the interesting failures happen.
Microsoft Entra ID
Your existing identity, your existing groups. IdentityServer where an application has to stand on its own.
Azure App Service with CI/CD
Health checks, response caching, HSTS and automatic backups, set up at rollout rather than after the first incident.
Weeks, not quarters, before you see it running. Then we stay.
We ship weekly to a staging environment you can open. No hand-off to a different team halfway through, and no phase where the project goes quiet for a month.
Scoping call
Thirty minutes to work out whether we are the right team for this. Often followed by a working session with the people who will actually use the thing.
Architecture outline
A short written document, usually three to six pages: data model, integrations, flow, security and cost. You keep it whether or not you go ahead with us.
Build
Simple tools in six to eight weeks. Mid-complexity in three to six months. Enterprise platforms in six to twelve. Weekly drops to staging throughout.
Production rollout
Into your Azure subscription, with CI/CD, monitoring and backups configured as part of the work rather than as an afterthought.
Ongoing operation
Support with proactive monitoring, security updates, and a direct line to the engineers who built it. Most of our clients have been with us for years.
The questions worth asking any supplier. Including us.
Do we own the source code?
Yes. Every engagement ships the full source code to a repository you control, and every deployment sends data directly to your own Azure subscription or on-premises SQL Server. There is no intermediate Proceptio-hosted layer holding your data.
Can you integrate with our ERP?
Yes. Our own NetSuite Sync product proves NetSuite integration at scale. We also integrate QuickBooks, Xero, Dynamics 365, SAP and Oracle via native REST or SuiteQL APIs. For proprietary systems we build custom connectors with incremental sync and automatic retry.
Why Blazor rather than React?
Blazor is the official Microsoft direction for .NET web apps and is on a long-term support track. For enterprise internal tools where a single team owns the full stack, it delivers faster, with fewer moving parts and a smaller JavaScript surface. For customer-facing apps that need a React-sized component ecosystem, we build on React or Blazor WebAssembly depending on the requirement.
What happens if we stop working with you?
Because the stack is standard Microsoft, any .NET-competent team can continue operating the application without disruption. We document architecture, deployment and operations in code and in Markdown in your repository. No proprietary languages, no closed-source runtime dependencies.
Anyone can ship a first version. The question is who is still answering the phone in year four.
Running for Heineken, Bailie Gifford, Cygnum Capital, DLM Finance, LPKF Laser & Electronics, SWO Netz, AMAG, MTI Technology, Farber Consulting Group, First Samuel, Gumiimpex-GRP, Techspace and Bomark, among others.
Start with the scoping call. Thirty minutes, no prepared pitch. Walk us through what you are trying to build or fix, and we will tell you honestly whether we are the right team for it, and roughly what it costs if we are.
If the right answer is a product you can buy instead of a system we build, that is a perfectly good outcome of the call.
Related
Our products
Eleven things you can buy rather than commission, from a NetSuite data platform to a fund-compliance system.
MCP & AI assistants
Lately these systems ship with an assistant layer, so your team can work them by asking.
Case studies
Named clients, with the outcomes we are able to publish.
