Capabilities in detail
Made-to-measure manufacturing breaks generic ERP. Every line is a different size, the price depends on area with a minimum threshold, the packing depends on length and weight — and half the value of the job is information that has to survive to the building site. We build for that case specifically.
Direction 01
Ten modules taken from systems running in daily production. Not all at once: a project starts with three or four and grows in the direction the business pulls it.
Dealer self-service portal, internal entry, and a documented REST API with per-partner keys for pushing orders in from an existing ERP.
Area pricing with a minimum billable area per unit and per order, product tiers, accessories and add-ons, and volume discounts computed from the customer's actual monthly activity.
Unit-level status on a touch-friendly floor view, photo and video evidence, defect reasons per component, and who did what and when behind every mark.
Lot numbers for film, copolymer, glass manufacture and glass lot are captured against the order and carried into passports, labels and documents.
Automatic box packing for flat goods and crate packing for glass, driven by length, weight and clearance — parameters an administrator edits without anyone touching code.
A carrier label per package, packing lists with per-package dimensions and weight, and shipment linking so a second order travels inside the first order's crate.
Accessory and consumable stock, warehouse-fulfilled orders with per-item picking, and supplier re-order documents generated from defects and shortages.
Branded PDF invoices, payment by card and bank debit with idempotent reconciliation, and payment marks that feed the discount tier.
Role-based access with per-user feature grants, account managers scoped to their own customers, and row-level security in the database so the rule holds even when a screen forgets it.
Email on the events that matter — order approved, glass arrived, shipment ready — to the role responsible rather than to everyone.
Configuration over code. Prices, thresholds, crate limits, packaging rules and material weights are administrator-editable parameters. The values that change with the market do not live in the source code.
Direction 02
Every unit gets a permanent, publicly readable record.
When a unit is marked complete, its passport is created automatically from data the system already holds. Nobody types anything twice.
A label printer produces the per-unit QR label as part of the normal production step.
The installer, the architect, the owner and the inspector scan the same code and see the same record. No login, no app.
The passport outlives the order, the invoice and — if it comes to it — the dealer.
On the regulation. The EU is phasing in digital product passports through the Ecodesign Regulation (EU) 2024/1781 and, for construction products, Regulation (EU) 2024/3110. Obligations arrive product group by product group through delegated acts, so the exact date for windows and doors is not yet fixed. The practical consequence is the same either way: the data has to be captured at the moment of production. A factory that is not capturing it now will be reconstructing it later from paper. Start with the data discipline, not with the deadline.
Direction 03
Most manufacturer websites are a brochure with a contact form. The form sends an email, someone copies it into a CRM two days later, and the enquiry is cold before anyone calls. We build the other kind.
Quote, sample and dealer applications land as typed fields — product, size, city, budget, campaign source — with spam protection and instant notification to the person responsible.
Energy calculators, area and price estimators, product configurators. The visitor gets an answer; you get a qualified enquiry with the specification attached.
Product catalogs, technical drawings, CAD files and specification sheets architects can actually find and download — maintained by your team, not by a developer.
The same login a dealer uses to order shows their pricing, their order history, their shipments and their documents. The public site and the portal are one system.
Technology
We use mainstream, well-documented technology and hand over the source code. If you ever want to bring the work in-house or move to another supplier, a competent developer can pick it up without an archaeology project.
Next.js and TypeScript for web applications and sites; Go for high-throughput services. Server-rendered, fast, and search-engine friendly by default.
PostgreSQL, with row-level security enforcing access rules in the database rather than only in the interface. Versioned migrations, so every schema change is reviewable.
Managed cloud hosting with automatic deployment from source control, preview environments for review before release, and nightly off-site backups of both the database and uploaded files.
Payments by card and bank debit, carrier labelling, CRM systems, accounting exports, and inbound or outbound APIs to an existing ERP.
Server-generated PDFs — invoices, technical submittals, packing lists, supplier orders, installation manuals — in your own layout and language, not a generic template.
Role-scoped access, database row security, input validation and rate limiting on public endpoints, encrypted storage of third-party credentials, and an audit trail on permission changes.
You own the code, the data and the accounts. Repositories, hosting and third-party services are registered to your company from day one.
AI where it earns its place. We use language models for the jobs they are genuinely good at — formatting and translating content, drafting product descriptions from specifications, extracting structured data out of supplier PDFs. We do not put them in the path of a price calculation or a production decision.
How we work
We do not sell eighteen-month implementations. The first release is a narrow slice that solves one real problem end to end, running on real orders.
We walk the floor, read your current documents and map how an order really moves — including the parts that live in someone's head. Output: a written process map, the scope of the first release, and a fixed price for it.
Week 1–2
One slice, built and shipped: usually order intake with production tracking, the passport pipeline, or the website with its lead flow. Reviewed with you weekly and running on real data before anyone calls it done.
Week 3–8
The remaining modules in your priority order, one at a time, each live before the next one starts. Your team is trained on the way in, not in a handover week at the end.
Month 3+
Monitoring, backups, updates and a named person who answers. Changes quoted individually or covered by a monthly retainer — your choice.
Ongoing
We quote after discovery — a fixed price per release rather than a range someone reinterprets later.
Book a call
Two sentences are enough: what runs on spreadsheets, paper or shouting today. You get an assessment shortly, not a brochure.