Custom software development
Custom software built around your business workflow
When standard tools do not fit the way your team works, Viken Data helps define and build focused software around the process. Start with the task, the people using it and the rules that need to hold—not a list of features you may never need.
Our work includes production tracking, controlled SQL data search, local work records and backup-validation evidence. We assess each enquiry against its actual requirements before recommending a custom build.
When a custom tool makes sense
The missing part is often the workflow, not another dashboard.
Bespoke software is worth considering when a repeated, important task depends on workarounds. The first question is whether a focused application will solve that problem better than adapting an existing tool.
Work is split across files
People copy the same information between spreadsheets, notes and reports. You need a consistent record of the work and a way to find its history.
The process has rules
A production step depends on earlier output, an exception needs a reason or a correction must preserve the original record. A generic checklist does not capture enough.
Your environment sets limits
Users may need a local application, approved database access, portable records or inspectable evidence. Those constraints belong in the design from the start.
What we can build together
Focused business tools with a defined job.
These are areas reflected in our existing software work. Your platform, users, data sources, deployment needs and acceptance criteria determine the scope of a commissioned application.
Production and workflow tracking
Track work through defined stages, show dependencies and shortages, and keep changes traceable. Useful when the question is what can move next and why something is blocked.
SQL data search and repeatable exports
Help users find approved data, repeat a known search and export results without rewriting the same query by hand. Database permissions and allowed operations remain explicit.
Local work records and document workflows
Organise jobs, assets, related records and supporting files around the way work is recorded and retrieved. Define storage, portability and recovery requirements alongside the interface.
Backup checks and evidence reports
Structure selected restore and validation checks, record what was tested and produce reviewable evidence. A bounded check must not be presented as proof of complete disaster recovery.
Need a public-facing website rather than an operational application? See our separate static website development service.
How a project takes shape
Agree the outcome, then make progress reviewable.
A useful brief explains the work. The delivery plan turns it into agreed scope, checkpoints and evidence of what is ready.
1. Understand the job
Identify users, current tools, repeated steps, exceptions and constraints. Assess whether custom development is appropriate and which unknowns need investigation.
2. Define the scope
Agree what is included, what is excluded, the delivery approach and how the result will be checked. Set pricing and timing against that scope.
3. Build and review
Implement the agreed workflow, review it at the planned checkpoints and test its rules and failure cases. Discuss scope changes before treating them as included work.
4. Check and hand over
Review the agreed acceptance criteria, deployment arrangements, documentation and known limits. Confirm maintenance responsibilities and any follow-up work.
Examples from our software work
Inspect the approach, not just the promise.
These project pages show software, screenshots and explicit limits. They are examples of our work, not claims of client results or ready-made solutions for every new project.
Available now · Freeware
Databases Searching Tool
The job: find known values across approved SQL Server scopes and repeat useful searches.
The software: a downloadable Windows application with saved profiles, scheduling, Search Memory and CSV or JSONL exports.
Working application · Active development
FlowLine
The job: track production and work in progress through ordered routes, dependencies and corrections.
The software: a working local-first application with production rules and audit history. It is not offered here as a finished public product or download.
Preview baseline · Active development
Proof of Restore
The job: check selected backup artifacts and retain evidence of the tested scope and result.
The software: an offline Windows preview for isolated, non-executing restore checks and local JSON and PDF evidence. It is not ready for public release.
Testable foundation · Active development
Workbench Vault
The job: connect work records, related objects and files in a local, user-owned workspace.
The software: tested storage, search and recovery foundations with a development interface. The complete V1 user workflow remains unfinished.
Budget and delivery
A quote needs more than a feature count.
The estimate depends on the workflow and its risks. A small interface can still require careful data migration, permission checks or recovery handling.
Scope and complexity
Users, business rules, data sources, integrations, supported environments and testing requirements affect the work. List what the first usable version must do.
Dependencies and timing
Access to representative data, feedback, third-party systems and deployment environments affects the plan. We clarify dependencies before agreeing delivery dates.
Handover and ongoing work
Documentation, deployment, licensing, source-code arrangements, maintenance and support need an explicit agreement. They are not left to an assumed default.
Before you enquire
Common custom software questions
You do not need a technical specification to start a conversation. A clear description of the current work is more useful than guessing at the implementation.
Can we start with one workflow?
Yes. A focused first scope can make the important rules and dependencies easier to review. We still need to understand the surrounding process so the first version does not create another disconnected tool.
Can the application work with our existing data?
That depends on the source system, permitted access and available interfaces. Describe the databases, file formats or exports involved. Integration and migration requirements are assessed before they are included in the scope.
Can the software run locally?
Local-first and offline workflows are part of our existing work. Whether they fit your project depends on the number of users, shared-data needs, target machines and recovery requirements.
What happens after delivery?
The project agreement defines the handover and any maintenance or support. Ongoing development, response times and third-party operating costs must be agreed explicitly; they are not automatically included.
Your software project
Tell us what your team needs to get done.
Send a short brief to support@vikendata.com. Describe the problem in your own words; we can clarify the technical questions from there.
- Who will use the software, and what task do they need to complete?
- Which tools, files or systems are involved today, and what is not working?
- What would a useful first version do, and what constraints must it respect?
- Do you have a target timeframe or budget range we should consider?
A non-sensitive outline is enough for the first email. Do not send passwords, access tokens or confidential customer records.