You need a Ruby on Rails company that understands existing software and can develop it further. Ruby has been part of 10KB since 2013. We work on business applications such as Werkplanner and help teams with maintenance, handover and technical improvements. You discuss what your product needs directly with developers.
Copyright in custom code we develop is transferred to you
A software development company led by two lead engineers
Agreements on handover, maintenance and ongoing development
A Rails partner for your application
At SGI Compliance, we gradually took over Werkplanner development from freelancers. The client was looking for several Ruby on Rails developers for maintenance and ongoing development. We make sure several developers know the application, onboard colleagues internally and document the development environment. Ewout and Roland contribute as lead engineers themselves.
At Smartfile, we improved authorisation, tests and deployments for existing Rails software. Such projects require more than writing new features: understanding existing functionality, investigating risks and combining technical improvements with the work users need.
We discuss the expertise and capacity your application needs during the introduction. A team creates room to share knowledge; we agree on timing and availability for each project.
Handover: we assess existing code, rights, accounts and documentation and arrange knowledge transfer with the current developer where possible.
Maintenance and development: updates, tests, releases and new features share a backlog and suitable ongoing agreements.
New development: we examine whether Rails conventions suit your portal, business rules and integrations. If another technology fits better, we discuss that trade-off.
Existing Rails software · SGI Compliance
Werkplanner supports project delivery with configurable forms and documents. SGI was looking for an ongoing partner with several Rails developers. We gradually took over development and continue expanding the application with the client.
A recorded development environment and internal knowledge transfer help colleagues join the work. Maintainability calls for decisions too: we are gradually moving parts of the separate frontend layer back towards Rails conventions with Hotwire and Stimulus. That modernisation is still in progress.
Explore Werkplanner at SGI ComplianceExisting Rails software · Smartfile
At Smartfile, the technical foundation made new features difficult to add. Access to patient records needed particular attention. We improved authorisation, mapped existing functionality and introduced automated tests.
We also improved the deployment process. This gave the team a foundation it could check more effectively when developing further. The example shows why work on existing Rails software sometimes starts with tests, permissions and releases before adding to the backlog.
Explore the improvements at Smartfile
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. Existing faults in software we take over are not automatically covered. 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. During a handover, we also check rights to existing code; our development does not automatically transfer those rights to you. 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
An approach for your application
01
What does your Rails application do, who develops it now and what is holding further development back? We examine code, dependencies, the database, background jobs, tests and deployments. For a new product, we discuss whether the Rails approach fits.
02
For a handover, we arrange access and knowledge transfer. For maintenance, we prioritise updates and the backlog; for a new product, we define an initial useful scope. We estimate work and record assumptions, budget and responsibilities.
03
You work directly with developers. Reviews, documentation and a recorded development environment help colleagues join the project. We deliver changes in agreed steps and make ongoing agreements for maintenance and support.
Our strength is software engineering. It is particularly valuable when the technology determines what your business can do and how reliably you serve your customers.
Unsure which route fits? We're happy to discuss whether our engineering expertise would add value to your project.
Ruby has been part of our work since founding the company in 2013. Werkplanner at SGI Compliance and Smartfile illustrate our work on existing Rails software: transferring knowledge, understanding business rules and improving tests and releases. You speak to the developers doing the work; Ewout and Roland contribute as lead engineers.
Yes, we are happy to discuss a handover. At Werkplanner, we gradually took over development from existing developers. We first assess code, accounts, rights and documentation and agree on the responsibilities we can carry. Where possible, we involve the current developer in knowledge transfer.
Updates, tests, releases and new features share a backlog. Reviews and documentation help several developers know the application. We discuss suitable capacity, priorities and support. For business-critical software, availability and support can be recorded in an SLA.
A business portal with accounts, forms and recurring workflows can fit Rails well. We also examine integrations, required interactions and the team maintaining the software. If we need to depart from Rails conventions in many places, another technology may make more sense. See also custom software.
New custom software typically starts at around €25,000. For ongoing development, a retainer of around €4,000 per month can be suitable. These are indicative starting points, not fixed packages. Maintenance and handover requests receive their own estimate based on scope, code quality and available knowledge.
We check rights to existing code; our development does not automatically transfer those rights to you. We do transfer copyright in custom code we develop for you. Existing bugs are not automatically covered by our software warranty. We record scope, warranty period and any repair work in advance.
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 what your application does, who develops it and what you want to improve. We discuss code, knowledge and next steps. 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.