01
Review the product, customers and operations
We examine the code, tenant structure, integrations, releases and known issues. Your current team helps transfer product knowledge.
Built by 10KB
Keep improving your existing SaaS product
Your platform already has customers. A new feature, handover or release affects people who rely on your product. 10KB helps you maintain and extend existing SaaS, with agreements on the roadmap, knowledge transfer and responsibilities.
An assessment of the existing situation and risks
Direct contact with developers who explain the choices
Clear agreements on scope, responsibilities and costs
Start with the existing situation
Continuity for your existing customers
We start with the code, customer environments and daily operations. How is data separated between customers, what roles exist and which integrations or subscriptions matter? We examine operations, error reports and release procedures before taking responsibility.
Together with your product owner and current developers, we arrange knowledge transfer. We agree on who handles incidents, how customers are informed and which risks need attention first. Taking over a platform also means transferring product knowledge and operational agreements.
Make the next step concrete
A roadmap that includes maintenance
Customer requests, technical improvements and maintenance compete for the same development time. We make these choices visible and decide together which changes add value first. Multi-tenant software needs checks on data separation, permissions and differences between customer environments.
For releases, we discuss test environments, acceptance, data migrations and fallback options. We also track whether important product processes still work. A retainer of around €4,000 per month can be a suitable starting point; the capacity needed depends on your product, users and roadmap.
In practice
Werkplanner: supporting different customers
Werkplanner is a multi-tenant application for remediation companies. We gradually took over development and made forms configurable so companies could support their own processes. Separate Review Apps helped assess changes. This combined product improvements with a better development process.
Read more
They really think things through with us and don't just build whatever is asked for.
Esther Radder
Product manager for Werkplanner at SGI Compliance Nederland
They don't just say yes; they're real sounding boards. Highly competent in their field.
Antoon Scheffers
IVBB
You've helped us greatly, both as a sounding board and in doing the work.
Toon Van Dooren
Lead innovation engineer at Savvii Managed Hosting
For the first time, software development feels simple, transparent and measurable to me.
Viktor Mirovic
Owner of TasteIndex
A company of developers
Talk to the people building your software
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 worksEwout Kleinsmann and Roland Boon
Two lead engineers at the helm
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
Three guarantees you can plan around
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. Existing faults in code we take over need separate agreements. 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
A ceiling on costs
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
The copyright belongs to you
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. Rights to existing code are checked during a handover. 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
Agree on the work step by step
From assessment to the next decision
You know your organisation and users. Together, we turn that knowledge into a practical technical approach with clear checks and decisions.
02
Agree on responsibilities and the roadmap
We document operations, incident handling, priorities and capacity. Initial improvements address risks and the needs of existing customers.
03
Release changes carefully and adjust
We check changes before deployment and track their behaviour afterwards. Together, we review customer feedback, progress and maintenance.
When does 10KB fit?
We are a good fit when software is important to your operations and you want to understand technical choices before committing to further work. You work directly with developers and provide someone who knows the product, users and priorities.
If an existing tool or a smaller change meets your needs, we discuss that too. For a standard content website or ecommerce system, a specialist in that platform may be a better fit. Our focus is custom software and its continued development.
What to know before starting
Yes, if the technology, access and rights allow a responsible handover. We begin with an assessment and agree with the current team on transferring code, product knowledge and operations.
We examine data separation, user permissions and customer configurations. Tests and acceptance environments help check differences between tenants. The required checks depend on the existing architecture.
Yes. This approach concerns a product already in use. For a new platform, we first discuss features, the customer model and technical choices. See our approach to building a SaaS product.
Ewout
Discuss your existing software
Tell us about your existing situation, the problems you face and the result you need. We will discuss the options and whether 10KB fits. Call +31 24 669 05 18 or email Ewout directly.