Custom Software & Web Application Development
Customer portals, internal tools and existing application development. Northerd designs, builds and documents business software from Kajaani, Finland.
Request a QuoteWho is this for?
For a business building a digital product, customer portal or internal tool. Existing applications can also be improved: a complete replacement is not necessary when a focused change solves the problem.
Customer portals and internal business tools
A customer portal might let a customer check an order or provide required information. An internal tool can bring a scattered work queue or reporting process into one view. These are possible use cases, not ready-made product packages. We define users, data ownership and the main workflow before implementation.
The interface and integrations belong together
Alongside the React interface, we design the data model, permissions and APIs. Backend choices depend on requirements: Node.js, Python or Rust. Integration planning covers failure handling, retries and data synchronisation, rather than only the successful API request.
Agreeing on the delivery
The specification sets out screens, user roles, integrations and acceptance criteria. Testing covers agreed workflows on mobile and desktop. Source code handover, deployment instructions, technical documentation and post-launch maintenance are agreed as part of the delivery.
What determines cost and timing?
The estimate depends particularly on integrations, permission complexity and legacy data migration. A focused first release can be priced separately from later development. We quote against an agreed scope rather than promise the same price or timeline for every application.
Includes
- Agreed user journeys, screens and permissions
- Required data model and scoped integrations
- Testing against acceptance criteria
- Agreed deployment, source code and technical guidance
Before you decide
Before work starts, know what you are buying, how it is priced and who will maintain the result.
When is custom software a better fit than an existing product?
Custom development may be justified when a key workflow, permissions or data exchange need awkward workarounds in an existing product. We first compare configuration changes, an integration and a custom application. The comparison includes licences, rollout and ongoing maintenance.
Can you take over an application built by another developer?
We start by reviewing source code, dependencies, access and deployment procedures. This establishes whether a focused fix or further development is practical. We also review documentation and tests. Scope is agreed against the findings before production changes.
What does application development cost, and can we start with an MVP?
An MVP is a focused first release built around the main user task. Screens, data models, permissions, integrations and testing determine the estimate. We agree on acceptance criteria and separate later features from the first delivery. Any paid discovery is agreed before it starts.
Do we receive the source code and can we change maintenance providers?
Source code, usage rights, documentation and service-account handover are agreed in writing. Third-party licences continue to apply. Deployment instructions and data exports support a transfer, while migration work and setting up a new environment are scoped separately.
What to bring to the first discussion
- Who will use the application and what must they accomplish?
- Which existing systems or APIs does it need to connect to?
- Do you have interface sketches, existing data or a target launch date?