You want customers or staff to work in one environment they can access through their browser. We build custom web applications for planning, order processing, customer interaction and other business processes. Together, we establish which roles, features and integrations you need and what the first release should do.
Copyright in the custom code is always transferred to you
A software development company led by two lead engineers
Clear guarantees covering costs, software and security
Software in the browser
A Glossary · In briefweb applicationA web application is a program you use through a web browser to complete tasks or process data. Processing can take place partly in the browser and partly on a server.Read more runs in your browser, without a local installation. It might be an internal planning tool, a customer portal or a product used by several organisations. Custom development fits when existing packages cannot support your process or lack important calculations and integrations.
We establish who needs to do what. A customer might submit a request, a staff member review it and an administrator change settings. We also enforce these permissions when processing data, so access does not depend solely on which buttons are visible.
Next, we determine which data the application manages itself and which comes from existing systems. Screens, calculations and integrations have separate places in the code. This lets us change and test individual features without changing the entire application each time.
Which tasks should users complete in the browser?
Which roles can view and change which data?
Which integrations, performance and security requirements matter?
Fintech · Getsby
For Getsby, we built an app that lets users buy, top up and manage virtual payment cards. Several financial providers work behind that app. Every movement of money needs to be traceable, including when a payment doesn't go as expected.
We made transactions traceable and structured the integrations so financial providers could be replaced. When a payment route proved insufficiently reliable in practice, we could replace it without rebuilding card management.
Early engineering decisions determine how much freedom you have later. Tests and monitoring help us keep checking that foundation as the product evolves.
Explore the engineering decisions behind Getsby
Manufacturing · Zetprofiel
For Zetprofiel, we built an order portal where customers and staff can draw steel profiles and calculate their properties. The software calculates materials, weight and price, then generates a work order for production. It replaces manual redrawing and gathering data from separate sources.
One engineering challenge was the geometry: how do you display dimensions and angles on complex shapes without labels overlapping? And how do you keep the drawing legible on a printed work order?
We separated the calculations from the controls and rendering. That let us add bend corrections later without rebuilding the drawing tool. Together with Zetprofiel, we use real profiles to keep improving the software.
Explore Zetprofiel's order portal
Esther Radder
Product manager for Werkplanner at SGI Compliance Nederland
Antoon Scheffers
IVBB
Toon Van Dooren
Lead innovation engineer at Savvii Managed Hosting
Viktor Mirovic
Owner of TasteIndex
A company of developers
Apart from Bas in sales and Linda in operations, everyone at 10KB is a developer. We don't employ project managers, designers or marketers. Software development is our craft, and our company is built around it.
You explain your requirements to the people writing the code. We make the technical choices understandable: what are the options, and what does each mean for reliability, security, costs and maintenance? You don't need to be a programmer to take part in those decisions.
Together, we choose what best fits your challenge. We keep considering those trade-offs throughout development, as usage grows, requirements change or a simpler solution becomes possible. Coordination, planning and explanation are part of our developers' work.
How direct contact with developers works
Ewout Kleinsmann and Roland Boon
Ewout and Roland were already programming together as students. That led to the founding of 10KB in 2013. They still do what brought them together: build software.
They contribute to all our projects every day. Their working day revolves around code: programming, reviewing colleagues' work and making technical decisions. When you discuss your software with them, you're talking to people who help build the solution themselves.
Ewout guides projects from the first outline through to delivery, keeping an eye on how the parts work together. Roland sets the technical direction and focuses on code quality, security and maintainability. You'll find them working alongside the other developers.
Meet the whole team
Agreements before the first line of code
Where a cost guarantee is agreed, the pessimistic estimate in the proposal sets the maximum for unchanged functionality and assumptions. If the work takes less time, you pay for the hours actually worked. We estimate new requirements separately.
We fix faults arising from our original development at no extra charge within the agreed scope and warranty period. The proposal specifies that period. We also agree on aftercare in advance: how to report problems and who handles them.
We address delivery findings from an agreed independent security audit at no extra charge within the agreed audit and project scope. The guarantee covers fixes to the delivered solution. New security requirements outside those agreements aren't included.
A maximum for an unchanged scope
Where a cost guarantee is agreed, the pessimistic estimate in the proposal sets the maximum for unchanged functionality and assumptions. If the work takes less time, you pay for the hours actually worked. We estimate new requirements separately.
Your investment, your software
We always transfer copyright in the custom code we develop for you. You can develop the software further, build an internal team or continue with another supplier.
We make that practical too, with access to the source code, documentation and necessary accounts. Wherever possible, hosting and external services are registered in your name. Third-party libraries and services remain subject to their own licences and terms.
You stay with us because the collaboration works. Your software doesn't tie you to us.
Our intellectual property agreements
From the first conversation to daily use
You know your product, users and ambitions. Together, we turn them into a technical approach. We explain the options and trade-offs so you understand what we're building and why.
01
We examine how customers and staff work today, which manual steps take time and where data is copied. Together, we define user roles, access and integrations with existing software. We also discuss which devices the application needs to work on.
02
We choose a first release that lets users complete a specific process. We estimate each part and identify assumptions, dependencies and risks. You can see what is needed to launch and which features can follow later.
03
You try working screens throughout development, using real examples from your organisation. We test calculations, permissions and integrations and discuss feedback directly with users. Before launch, we agree on hosting, monitoring, maintenance and further development.
Our strength is software engineering. It fits web applications where processes, permissions, calculations and integrations determine how the software works every day.
Unsure which route fits? We're happy to discuss whether our engineering expertise would add value to your project.
A website mainly helps people find information. In a web application, users complete tasks: planning, reviewing requests, placing orders or managing data. That calls for user roles, stored data and often integrations with other software.
For a new build, our starting point is generally around €25,000 or more. Roles, screens, calculations, integrations and data migration determine the actual budget. We estimate individual parts with assumptions and risks, and invoice monthly in arrears for hours worked. A retainer of around €4,000 per month may suit ongoing development; it is not a fixed package. Read our budget and pricing model.
We choose based on your processes, existing systems and maintenance needs. For Zetprofiel's profile editor, we use React and TypeScript. Another application may call for different choices. We explain what those choices mean for testing, security and later changes.
Yes, where those systems provide access through an API or another suitable interface. We first examine which data needs to move, which system is the source of truth and what should happen when an exchange fails. Read about having an API integration built.
The schedule depends on what the first version needs to do, its integrations and any migration of existing data. We agree on what needs to be usable first and the steps required to get there. On your side, we need someone who knows the product and its users, can set priorities and has time to review work in progress. We take that availability into account when planning.
Yes. For Werkplanner, for example, we gradually took over development from the existing developers. We first examine the code, documentation, hosting and dependencies. Then we discuss what can stay, where the risks lie and how to organise a responsible handover.
Our developers also work on the screens and how people use the software. They draw on real workflows and feedback from users, as we did with Zetprofiel's drawing tool. If specialist design or additional user research is needed, we discuss how to arrange and budget for it in advance.
We agree in advance on how to report problems and what the software warranty covers. We make separate arrangements for ongoing maintenance, security updates, hosting and availability. For business-critical software, those can be recorded in an SLA. See our approach to maintenance and support.
Bas usually handles the initial introduction and learns about your requirements. Ewout or Roland joins for the technical discussion. During development, you work directly with the developers. If you'd like to raise a technical question straight away, you can also email Ewout or Roland. An introductory conversation comes with no obligation.
Ewout
Tell us which processes you want to support, who will use the application and which systems it needs to connect to. You do not need a detailed technical plan. Call +31 24 669 05 18 or email Ewout directly.
CONTACT
Have a question or want to discuss your software? Leave your details and we will get back to you soon.