Custom software development
Scope
What is included
Every project has a different scope; the quote lists each included item one by one.
Last updated:
- A written description of the need and the scope of the first release
- A web application, admin panel or server-side service
- API integration with existing systems where needed
- Demonstration on a test address and approved release
- Setup and usage documentation, change notes
- Written handover of the code and access details
Preparation
What we ask from you
- A short account of how the work is done today
- Sample screens, Excel files or documents if you have them
- Access details or API documentation of the systems to be integrated
- A person who makes the decisions
Process
With your approval at every step.
- 01
Listening to the work
We talk about today's workflow, where you get stuck and what the software should change.
- 02
Written scope
We write what is in the first release and what is not, and prepare the quote accordingly.
- 03
Development in small parts
We start with the smallest part that works and show each step working on a test address.
- 04
Handover and documentation
We hand over the code, setup and usage documentation and change notes, and release with your approval.
Details
About the service
When custom software is needed
If an off-the-shelf program covers most of your work, using it is usually the better choice. Custom software makes sense where a ready-made solution does not fit your workflow: when you have to enter the same data by hand into three separate files, when two systems need to exchange data, or when you have an approval or reporting routine specific to your business. We first listen to such a job and assess together whether it really needs software; if it does not, we say so. A small setting in an existing tool or a script may be the solution; saying so at the very start spares you from paying for software you do not need and makes trust as solid as the written scope. If software is needed, we explain why with a concrete example.
What we build
- Admin panels and internal tools: Interfaces that bring orders, stock, customers or request tracking onto one screen.
- Web applications: Applications that your customers or staff use in the browser, with sign-in and permission rules.
- Server-side services and APIs: Services that other systems call, which process or transform data.
- Integration: Data exchange with your existing accounting, CRM or e-commerce system.
How we work
We first produce a written scope: which screens and functions the first release has, which are deliberately left out, where the data comes from and who signs in with which permissions. This document is the basis of both the quote and later discussions. We split development into small parts and show each part working on a test address. A change that touches the live system does not go out without your approval. That way you see early whether the direction is right, without committing to a large budget. At every stage you have something that works, not just a design or a promise. If a part does not turn out as you expected, we change it early and cheaply, not late and expensively. When the scope changes, we write it into the scope document and review the quote together again.
What you receive at handover
Along with the working software, the setup and usage documentation, change notes and access details stay with you in writing. If you want to continue with another team tomorrow, you do not start from scratch. We write the terms of use and transfer of the code we write for you in the contract before work begins.
What determines time and price
Price and time depend on the number of screens and functions, user roles and permission rules, the number of systems to connect and the quality of their documentation, data migration needs, reporting and how custom the design is. For uncertain parts of the job we may first suggest a small review or a prototype, so that the scope of the real work rests on something we have seen rather than a guess. The quote is prepared from the written scope and is discussed again if the scope changes.
If the software is going to become a product, see from prototype to product; if you need a mobile interface, see mobile app.
Pricing
The price is settled in a written quote
Because it depends on the scope, we do not write this service's price on the page. Tell us what you want; we will send the scope and price line by line in writing. A quote does not commit you.
Related services
Often considered together
FAQ
Frequently asked questions
Who owns the code we write?
We write it in the contract separately. The terms of use and transfer for code written specifically for you are settled before work begins.
How is the price set?
We first write the scope together; the quote is prepared from that written scope. If the scope changes, the quote is discussed again.
Can we start with a small job?
Yes, that is our preference. We start with the smallest part that works and grow it as we see it working.
Can you improve my existing software?
We first review the code and the architecture. We explain in written findings whether continuing makes sense, and write a scope accordingly.
Do you work remotely?
Yes, most work is done remotely. We hold meetings online.
Let us send you the scope in writing.
A quote does not commit you; we settle the scope together and price it line by line.