Custom software
Our custom software service builds software you own for processes that ready-made tools do not fit. Timelines depend on scope. The scope and finish date are written into a definition of done on day one, and the code lives in your repository from the start.
Who is custom software for?
Custom software is for companies whose work does not fit a ready-made tool. Typical clients run orders, production or quotes through spreadsheets and email, or glue several tools together by hand.
We first check whether an existing product would do the job. If it would, we tell you. If you have several quotes on the table, how to compare software quotes lists what to check.
What do we build?
We learn how your work runs today and turn it into software. Screens, data, permissions and connections to other systems are designed together. We usually write it in Laravel and Vue, and use Python for data-heavy or reporting work.
We do not deliver a large project in one go. The first part solves the process that wastes the most time. We describe this approach in how to build an MVP. Each part gets its own definition of done, a signed list of what finished means. With us there is no 90 percent. It is done or it is not.
If another team left you with half-finished software, you may not need to start over. See project takeover.
What is included
-
Process analysis
We map how the work runs today by talking to your team.
-
Screens and data design
You approve the screens. We decide early how data is stored.
-
Roles and permissions
Who can see and change what is defined in the software.
-
Connections
We connect accounting, e-invoicing, email or your existing tools.
-
Code and server in your name
You can always continue with another team.
How the project runs
- 01 You write, we reply within a business day Day 0 you describe the problem. Day 1 we reply. Day 2 we listen for 30 minutes to how the work runs today.
- 02 One-page quote and definition of done Day 4 you get a quote for the first part. Day 5 the definition of done is signed and work starts.
- 03 Build You approve the screens, then we build. You see progress on a staging environment every week.
- 04 Testing We test with your team using realistic data and tick off every item.
- 05 Go live and handover We go live on the promised date, train your team and hand over logins and setup notes.
Who keeps the code after delivery?
You do, because it has been in your repository since day one. The same goes for servers and domains, as we explain in who should own your domain. We fix bugs for free for 30 days. Each next part gets a new one-page quote and a new definition of done.
Monthly maintenance and support is optional. If you want to leave, one email is enough.
Frequently asked questions
How long does custom software take?
It depends on scope. We split large work into parts of a few weeks, each with its own date.
What drives the price?
The number of screens and processes, user roles and the systems to connect. The quote is one page and nothing is added later.
What if the scope changes midway?
We write down the new request and its impact. It moves to the next part, or we update the definition of done together.
Can we move the software to another company?
Yes. Code and server are in your name, and we hand over setup notes.
How will our team learn the new software?
We give your team a short training before go-live. A few of your people will already have used it during testing. In the first weeks, we answer the questions that come up.
Custom software or an off-the-shelf tool?
If your work fits an existing tool, that tool is usually faster and cheaper. Custom software makes sense when your team will not use the tool, your workflow does not fit its steps, or you connect several tools by hand. We tell you which fits on the first call.
What should we prepare before we start?
Spreadsheets, forms or email examples that show how the work runs today are the best start. Write down who will use the software and which task wastes the most time. No detailed specification needed; we write it together.
Which technologies do you use?
Usually Laravel and Vue, with Python for data processing and reporting. These are widely used, easy-to-maintain tools, so a developer after us can read the code too.
Can we start with a small first version?
Yes, and we often recommend it. The first part solves the process that wastes the most time and goes into use quickly. This is called an MVP. Later parts are planned from how your team actually uses it.
Is there support after delivery?
Yes. We fix bugs for free for 30 days after delivery. After that, monthly maintenance is optional. If you want to leave, one email is enough.