Approval workflows
Requests, multi-step approvals, and notifications with a full history.
Every business has one: a shared spreadsheet with macros, color codes, and a single person who understands it. We turn it into a proper application with permissions, history, and an API.
Same workflow, real database, proper permissions, no more 'who overwrote row 400?'
Requests, multi-step approvals, and notifications with a full history.
Live numbers from several systems in one place.
Small services that move data between tools reliably.
Secure access for customers, suppliers, or agents.
If a spreadsheet has a 'DO NOT TOUCH' tab, it's already software. It just doesn't have tests.
Off-the-shelf tools cover most needs, and we recommend them whenever they fit. But every business has a few processes that make it different: a quoting method, a scheduling rule, an approval chain. When those are forced into generic tools, they end up in spreadsheets, email threads, and workarounds that only one person understands.
Custom software makes sense for exactly those processes. A focused internal tool can replace a fragile spreadsheet, connect systems that don't talk to each other, or give a team one screen instead of five.
We keep custom builds small, well-tested, and connected to the systems you already have, so they remain an asset rather than a maintenance burden.
| Situation | Usually |
|---|---|
| Standard process (payroll, email, accounting) | Buy |
| Standard process with small tweaks | Buy and configure, or extend |
| Process that differentiates your business | Build |
| Glue between existing systems | Build a focused integration |
| Spreadsheet that has become critical | Build a proper tool |
Quoting, scheduling, approvals, and operations dashboards built around your process.
Connectors between your ERP, CRM, e-commerce, and partner systems.
Self-service access to orders, documents, and status.
Dashboards and exports that pull from several systems at once.
Step 01
Watch the current process, collect examples, and agree the scope.
Step 02
A clickable prototype to confirm screens and flow before code.
Step 03
Two-week iterations with a demo at the end of each.
Step 04
Data migration, training, and a supported go-live.
Step 05
Fixes and improvements under a maintenance plan.
The first pitfall is rebuilding something that already exists. We check available tools and your ERP's capabilities before writing any code.
The second is building without the people who do the work. Users join demos every iteration, so the tool fits their real process rather than an assumption.
The third is software with no owner. Every tool needs someone responsible for priorities and a plan for maintenance after launch.
| Measure | Why it matters |
|---|---|
| Time per task | Before and after the tool |
| Error rate | Mistakes the tool prevents |
| Adoption | Share of the team using it daily |
| Support requests | Signs of confusion or missing features |
Picture an engineering firm that prices projects in a spreadsheet with dozens of tabs. A custom quoting tool captures the same logic, pulls rates from the ERP, keeps every version of a quote, and generates the client PDF.
Estimators work faster, the formulas are tested, and a quote can be traced back to the inputs that produced it.
Success is a tool your team prefers to the spreadsheet it replaced, with fewer errors and a clear owner for its future.
| Layer | Common choice | Why |
|---|---|---|
| Interface | React and Next.js | Fast, accessible, widely understood |
| Services | Python or Node.js | Mature libraries, easy to hire for |
| Database | PostgreSQL | Reliable, flexible, and free |
| Hosting | Your cloud or ours | Matched to your policies and budget |
| Integration | REST APIs and webhooks | Works with Odoo and most SaaS tools |
Myth: Custom software is always expensive.
Reality: A focused tool that replaces a fragile process often pays back quickly. The expense comes from unclear scope, which discovery prevents.
Myth: Once built, it's finished.
Reality: Software needs updates for security, dependencies, and changing processes. A modest maintenance plan keeps it healthy.
Myth: Low-code tools make developers unnecessary.
Reality: Low-code is great for simple apps. Complex logic, integrations, and scale still benefit from conventional code.
Every tool we build lives in version control, ships through an automated pipeline, and comes with tests on its critical paths and a short guide for whoever maintains it next. Dependencies are kept current, so the tool doesn't quietly become a security risk.
Internal tools are often built quickly and then maintained for years. We follow the practical test pyramid described by Ham Vocke: lots of small, fast unit tests, a moderate number of coarser tests, and very few end-to-end testsSource [1]. It keeps changes cheap long after launch.
Accessibility matters for internal tools too, because your colleagues use them every day. We build to WCAG 2.2, the W3C Recommendation published in December 2024, built on the four principles of perceivable, operable, understandable, and robustSource [2].
Build vs buy
When to build custom software, when to buy SaaS, and when to extend an ERP. A practical decision framework with the costs people forget.
WebDesign systems
Design systems with tokens, accessible React components, documentation, and Odoo OWL views that keep products consistent.
OdooCustom Odoo modules
Upgrade-safe custom Odoo modules in Python and OWL: inheritance only, tested, documented, and OCA-style. No core patches, ever.
Next step
Thirty minutes with an engineer, no slide deck required. You'll leave with a clearer picture, whether or not we work together.