Development · Engineering
Custom software development built around how your business works.
Development work that exists to run operations: order processing tools, portals, field and warehouse apps and the integrations between them. Usually with SAP Business One® somewhere in the picture, but not always.
What we build
- 01Custom softwareInternal systems for processes no packaged product models.
- 02Web applicationsPortals, dashboards and business apps that people use all day.
- 03Mobile applicationsField, warehouse and sales apps, built for poor signal and gloves.
- 04API developmentVersioned, documented contracts other systems can rely on.
- 05System integrationMiddleware between SAP Business One and everything else, built to be watched.
- 06Business automationRemoving the steps a person only performs because software will not.
- 07Database systemsSchema design, reporting databases and the queries behind them.
The constraints
Operational software is a different job from a website
Everything below is why. None of it is visible in a portfolio, and all of it decides whether the thing is still working in three years.
- 01
It runs the business
When an order-entry screen is down, orders stop. That is a different reliability requirement from a page that is slow to load.
- 02
The data outlives the app
Whatever we build, the records it creates will be queried for years, probably by something else. Schema decisions are the long-lived ones.
- 03
The network is not reliable
Warehouses have dead spots and vans drive through them. Software that assumes connectivity fails exactly where it is needed most.
- 04
Someone else supports it
In three years the person maintaining this will not be the person who wrote it. Legibility beats cleverness every time.
- 05
It has to survive upgrades
SAP releases new versions of SAP Business One. Anything built on unsupported behaviour becomes a crisis on somebody's upgrade weekend.
- 06
Users did not choose it
Nobody signed up for the warehouse app. If it is slower than the clipboard it replaced, it will be worked around.
How we build it
Five layers, and a firm opinion about what goes in each
Having an opinion about where logic lives is most of what separates engineering from assembling a website. Point at a layer.
Layers talk downward, never sideways. That single rule is what lets one of them be replaced without rewriting the others.
Rules · Workflow
Business logic
The rules the business actually runs on, in one place, testable. When a rule changes it changes once rather than in four clients.
What belongs here
- Pricing and eligibility rules
- Workflow and state transitions
- Calculations and derivations
- The tests that prove they work
What does not
Anything duplicated from SAP Business One. Where SAP Business One owns a rule, we ask it rather than reimplementing it and hoping the two agree.
Practice areas
Where the work is grouped
Most projects touch more than one of these. They are scoped and quoted together.
- 01Custom SoftwareInternal systems, order processing, workflow tools.
- 02Web ApplicationsPortals, dashboards and business web apps.
- 03Mobile ApplicationsField, warehouse and sales apps, online and offline.
- 04System IntegrationAPIs, middleware and scheduled synchronization.
- 05Design & MarketingFlyers, catalog sheets and campaigns from live data.
Delivery
How a development project runs
- 01
Discover
We understand the business goal, the users and the systems the work has to fit into.
- 02
Plan
Scope, features and a roadmap are defined and written down before estimates are given.
- 03
Design
Screens, data flows and integration points are designed with the people who will use them.
- 04
Develop
Clean, documented code against supported interfaces, delivered in reviewable increments.
- 05
Test
Functional, integration and performance testing on realistic data before anything reaches users.
- 06
Launch
Deployment, cutover and hands-on support during the first days of live use.
- 07
Support
Maintenance, monitoring and improvements under an agreed support arrangement.
Stack
What we actually work in
Listed because we use these in delivery, not to fill a page. If your environment runs something else, ask and we will say honestly whether we are the right team.
- SAP Business OneSDK, DI API, Service Layer
- SAP HANADatabase and analytics
- Microsoft SQL ServerDatabase, queries, reporting
- MySQLWeb application databases
- .NET and ASP.NETServices, middleware, back-office apps
- REST and Web APIsIntegration and application interfaces
- React and Next.jsWeb applications and portals
- HTML, CSS and JavaScriptWeb front ends
- SAP Crystal ReportsOperational and financial reporting
Adjacent
Design and marketing production
Flyers, catalog sheets and campaigns generated from the item and price data we already manage for you. A support service for existing clients, not an agency offering, and it is on its own page rather than mixed in with the engineering work.
Next step
Describe the process, not the software you think you need.
Tell us what has to happen, who does it today and where it breaks. The specification is our job, and it is usually smaller than expected.