Cross-platform spreadsheet
A desktop spreadsheet for Windows, Linux, and macOS whose Rust engine recalculates a million formulas in milliseconds.
8 weeksApr 2026
R&D, native modules, and developer tools.
Research and development is the work before a product is certain: proving that a technique works, measuring whether a target can be met, or building the module and tooling that make it possible.
Developer tools
- Command-line tools and build toolingSingle-binary tools for your pipeline, cross-compiled for Linux, macOS, and Windows.
- Libraries and SDKsA documented API with tests and examples, published to crates.io, npm, or PyPI.
- Parsers, language servers, analyzersEditor support and static checks for your own format, configuration language, or data files.
Native modules
- Rust inside PythonThe slow loop becomes a compiled extension (PyO3, maturin) with the same API. Measured before and after.
- Rust in the browser (WebAssembly)Parsing, simulation, and rendering in the page itself, without a round trip to a server.
- Rust in Node.js and desktop appsnapi-rs modules and Tauri backends for file processing, local databases, and hardware access.
R&D
- Feasibility studyCan the target be met at all? One to two weeks of measurement ending in a written answer with numbers.
- Proof of conceptA working prototype of the risky part, built to be measured, then hardened into a product or dropped.
- Algorithms and simulationsScheduling, optimisation, signal processing, and manufacturing or process simulation.
Built in the lab:
A cross-platform spreadsheet whose Rust engine recalculates a million formulas in milliseconds, and a C++23 entity-component library for games and simulations.
ECS library for game development
A header-only C++23 entity-component-system library with dense storage and measured iteration.
5 weeksFeb 2026
- raylib
How we work.
- 01Understand the workload first
We read the code and measure a baseline on real data before we write anything, and turn the question into something testable.
- 02Modern tools, chosen for the job
Rust where it helps, and the team's existing language everywhere else, so the module fits the codebase.
- 03No overengineering
The smallest prototype that can settle the question. Everything around it stays a stub until the answer is in.
- 04Measured, not promised
Results come from benchmarks, reported under stated conditions with the limitations. A clear no is a valid outcome.
- 05Less consulting, more building
Something you can run from the first week, so decisions are made on a working prototype.
- 06Direct communication
You talk to the engineers doing the work, and you get a written status update every week.
- 07Code your engineers can continue
We work in your repository, review with your team, and leave tests and documentation behind.
- 08Fair price, no surprises
A fixed number of weeks at €1,500 a week, agreed up front. When the answer is yes, the tool or module is built as a first release at the MVP package price.
What happens after you write to us.
- A reply within 24 hoursAn engineer replies with first questions. We then discuss the design and architecture together and turn the idea into a clear plan, by email, on a call, or in person.
- Written proposal (PRD)The scope and a timeline with clear milestones, within a week.
- Transparent work and daily communicationWe send daily updates, and you have direct access to the engineers, so decisions and adjustments happen quickly.
- Launch and handoverWe deploy the release, and your team accepts it against the criteria agreed in the proposal. You receive the source code, the documentation, and access to everything we set up, so any engineer can continue the work.
- Long-term support and evolutionAfter launch, we maintain the application and extend it as requirements change. The first three months of maintenance are included.
MVP package: the first production release
€9,200€11,500−20% founding client offer
6–8 weeks from agreed scope to launch
- Consultation and project scoping, free
- UI/UX design
- Frontend, backend, and integrations
- Testing, deployment, and documentation
- 3 months of maintenance, then €300 / month
- Source code and a clean handover
What does founding client mean?
After launch, you agree to a short written interview for a case study. We agree what gets published before the project starts.
EU companies with a VAT number pay exactly this amount (reverse charge).
Questions about this service
What counts as a useful investigation?
A question with a testable outcome: whether a calculation can meet a latency target, a local workflow can survive disconnection, or a native module helps a particular workload.
Can you promise a particular speedup?
Only after measuring the workload and testing an approach. We establish a baseline first and report improvements under stated conditions.
Do you work in areas you have not covered before?
Yes, and we say so. For IoT, embedded, simulations, or other unfamiliar domains we take on a defined feasibility question, agree the unknowns and the time limit, and report what we find.
Is the prototype production-ready?
Not automatically. We distinguish the experiment from the hardening, integration, and operational work needed for production, and estimate that work separately.