People need to enter, review or track status
- staff check-in and check-out
- processing requests
- managing tasks
- internal planning
- customer or staff portal
- tracking status
- approvals
Selected custom solutions
Custom software built around how the work actually happens.
OmniTechs is a founder-led custom software development company in Groningen. We design operational tools, portals, dashboards, integrations and focused digital products when standard software does not fit the workflow.
Solution Sprint — €1,250 excl. VAT
When is custom software justified?
Custom software can be responsible when a valuable workflow repeatedly depends on workarounds, disconnected systems or constraints that suitable standard tools cannot address. The first task is to verify that boundary, not to assume a build is necessary.
Worth investigating when
- teams repeatedly enter or reconcile the same information
- critical work sits outside the system that should support it
- an integration is missing or operational exceptions are unmanaged
- the distinct workflow or product model creates business value
Use an existing tool when
- a maintained product already covers the important workflow
- the process itself is not yet stable enough to define
- the expected value does not justify ownership and maintenance
Which of these is closest to your problem?
Too much work is done by hand or twice
- copying data between systems
- keeping Excel up to date by hand
- the same admin every day
- processing documents
- automatic notifications
- manual status updates
Systems need to exchange data automatically
- CRM ↔ accounting
- webshop ↔ ERP
- form ↔ internal system
- stock synchronisation
It genuinely needs to work as a mobile app
Describe the task, target devices and what must work without a connection. I assess the appropriate form; a requested device feature does not by itself establish a need for a native app.
- camera
- location
- push notifications
- offline use
- device-specific functions
I do not know yet what I need
You do not have to. Describe what is going wrong now, or what takes more time than it should. We first decide which solution is the logical one.
Tell us what needs to work betterRelevant offer at a glance
Solution Sprint
Paid scope work€1,250 excl. VAT
An organisation with a non-standard process or product problem that first needs to investigate users, dependencies, risks and scope.
Independent project work that clarifies the problem, users, dependencies, risks and scope before an implementation price is provided.
- A 60–90-minute problem and process workshop
- Current-state workflow map
- User and stakeholder definition
Implementation not included
Annual plans for digital work
Part of a wider annual plan?
When software, automation and integrations add up to a year of work, COMPANY (from €5,000/year excl. VAT) can combine implementation and ongoing work. The proposal selects what is needed.
COMPANY
Build around how your company works.
From €5,000/year excl. VAT
A scoped technology plan for your website, specialist content and SEO, internal software, automation, mobile applications, AI and connected hardware.
The proposal selects the building blocks; not every capability is in the starting price.
- A written proposal that selects the building blocks your company needs
- Defined implementation for the plan year
- Defined ongoing work: operation, maintenance and agreed improvements
COMPANY is not discovery only: the plan covers implementation and ongoing work. The Solution Session and Solution Sprint stay separate and optional.
Just this module?
That works. Request this module on its own, without an annual plan. A paid Solution Session or Sprint is optional.
Request this module on its own: Custom softwareCompare the plans
Web applications
Portals, dashboards and focused browser-based workflows
A web application can let authorised users manage data, complete tasks or collaborate through a browser. Suitable shapes include an internal operational tool, customer or supplier portal, dashboard, controlled workflow or a bounded first product release.
The first release should prove the critical user task before roles, integrations, billing or secondary features expand the operating burden.
Example workflow
Staff check-in and check-out
Employee checks in
The shift becomes active
The supervisor sees who is present
Exceptions are flagged
Check-out closes the shift
Service company
New request
Staff member assigned
Status updated
Customer notified
Task completed
API integrations
Move information between systems without hiding the exceptions
A focused API integration can reduce duplicate entry when two maintained systems already own the relevant work. Reliable delivery also needs authentication, source-of-truth rules, duplicate handling, safe retries, monitoring and a clear response when an external service changes.
Documentation, suitable access, data examples and the intended source and destination must be examined before scope and implementation can be priced responsibly.
Professional recommendation
“Whether it was optimizing component performance or integrating new features, Sina approached each challenge with a strategic mindset and a hands-on attitude.”
Workflow automation
Automate defined work with visible controls
Rules and ordinary integrations should be used when they are sufficient. AI is considered only as a capability inside a controlled workflow when language, documents or variable input make it useful.
Important decisions retain an appropriate human approval point. Data boundaries, failure states, monitoring and recovery must be clear before unattended operation is treated as dependable.
Example workflow
Incoming email
Email arrives
Details are extracted
Checked
The system is updated
Exceptions go to a staff member
Mobile applications
Use an app only when the use case benefits from one
A mobile application can be appropriate for frequent use on the move, notifications, offline behaviour, device capabilities or a connected physical workflow. If a responsive web application meets the need with less operating complexity, OmniTechs recommends that route instead.
Platform choice follows user behaviour, device requirements, integrations, support capacity and app-store responsibilities—not the platform that sounds most impressive.
Independent scope work
Start with evidence through a Solution Sprint
The Solution Sprint is not an extended sales conversation. It is independent project work that investigates the problem, users, dependencies, risks and scope before an implementation price is provided.
Implementation is not included, and you are not required to commission it from OmniTechs. No implementation price is promised before the necessary scope work is complete. If a simpler existing solution is sufficient, we recommend it.
- Map the current workflow and affected people
- Review requirements, data, integrations, risks and assumptions
- Make the critical uncertainty visible with a prototype, technical test or system diagram where useful
- Document scope boundaries, architecture direction and a phased or fixed-scope proposal
Professional recommendation
“Sina is a professional programmer with a sense of investigating anything and figuring out how to solve problems. When he faces a challenge he will find a solution.”
Ownership and operating responsibility are part of the design
A proposal should identify accounts, data, source code or deliverables, third-party dependencies, access, deployment responsibility, error handling, support boundaries and recurring costs before implementation begins.
Customer content, business data and domain remain the customer’s property. Project-specific intellectual-property and licensing terms are confirmed in writing for the applicable engagement.
Does your own application need to expose an API?
Connecting two existing systems is different from providing an interface for your own application. Define what a portal, mobile client or partner may read or change, how rejected requests are handled and who manages access and future changes.
Telegram is one possible channel
If people already use Telegram, a bot may collect a request or notify its owner. Decide who may use it and who follows up incomplete input. A message does not replace the workflow or authorize every action a bot could technically perform.
Installation and field-service workflows
A planner assigns work, a technician records completion, and the office needs complete hours and materials before processing the record. Start with the missing handover and the existing planning or accounting package. OmniTechs does not sell a ready-made field-service platform.
When the process is not clear yet
A request may wait because nobody knows who should approve it. Start by identifying the responsible person and missing information. Working alongside the team is optional when a conversation and examples cannot explain the exceptions; you can enquire directly about a defined task.
Brengo: an owned product in a live pilot
The Dutch case shows requester and provider roles around a transport task, with task status and controlled actions. Brengo is an OmniTechs product, not a completed customer commission; no adoption or customer outcome is claimed.
Try a request before discussing automation
The quotation-flow demo uses fictional inputs to show validation and human approval. It runs locally in the browser and sends no real quotation or CRM action. Use it to identify where a person still needs to decide.
Frequently asked questions about custom software
When is standard software sufficient?
Standard software is usually the better choice when a maintained product covers the important workflow without harmful workarounds or unacceptable ownership constraints.
When is custom software responsible?
It can be responsible when the workflow is understood, suitable existing tools do not fit, the expected value justifies ownership, and the organisation can support the resulting system.
What determines implementation cost?
Users, roles, workflows, data, integrations, security, failure handling, operating requirements and unresolved risk determine the scope. OmniTechs does not publish an implementation price before the necessary investigation is complete.
What do I receive from the Solution Sprint?
The canonical Solution Sprint card on this page lists the current deliverables. They include documented investigation of the workflow, users, dependencies, risks and scope, with a prototype, technical test or diagram where useful.
Am I required to commission implementation from OmniTechs?
No. The sprint is independent project work. Implementation is not included and you are not required to commission it from OmniTechs.
Can an existing system be improved instead of replaced?
Often, yes. A configuration change, focused integration or small workflow improvement may solve the defined problem with less cost and risk than replacement.
Is AI required for workflow automation?
No. Deterministic rules and ordinary integrations are preferred when they are sufficient. AI is used only where variable language or content justifies it and the workflow has appropriate controls.
Bring the workflow, not a predetermined stack.
Describe who is affected, where the work gets stuck and what must demonstrably improve.