Skip to content
TRDThe Research Desk, home

02 · Software

Custom software for the problems packaged tools don't solve

Some requirements don't fit a category. A data pipeline, a desktop tool for an offline workshop, a scraper that feeds your CRM. We specify the problem in writing, agree on what done means, and build it.

Free first conversation · No obligation · You own the code

§ 01Is this you?

You're likely in the right place if…

  • 01You've looked for a product and none of them do the one thing you need.
  • 02A manual process is costing more each month than building a tool would.

Sound familiar? Tell us which one on WhatsApp (opens in a new tab) and we'll suggest where to start.

§ 02Deliverables

What we build

  1. 01

    Web applications

    Browser-based tools for internal teams or customers.

  2. 02

    Desktop applications

    Cross-platform desktop software when work happens offline or needs local hardware.

  3. 03

    Data pipelines

    Collection, cleaning and enrichment of data from files, websites and APIs.

§ 03Approach

How we build it

  1. Written scope

    Fixed deliverables, timeline and price, approved before any code is written.

  2. Full handover

    Source code, documentation and deployment instructions, in your repositories.

Typical stack

  • TypeScript
  • Node.js
  • Python
  • .NET
  • PostgreSQL
§ 04FAQ

Questions about custom software

01Can you build a desktop application?

Yes, when the work needs to run offline or talk to local hardware. For most business tools a web application is simpler to deploy and maintain, and we'll recommend that when it fits.

02Can you collect data from websites or files automatically?

Yes, from files, APIs and permitted web sources, with cleaning and de-duplication. We only collect data you're entitled to use.

03How do you price custom work?

After a short study we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it.

04Will we get the source code?

Yes. Source code, documentation and deployment instructions are handed over in your repositories when the project is paid.

05How is the price decided?

After a short study of your process we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it; payment is typically 50% to start and 50% on delivery.

06Who owns the work when it's finished?

You do. Code, accounts and documentation are handed over in your name once the project is paid.

Next step

Ready to talk about custom software?

Describe the system you need, or the spreadsheet you've outgrown. We'll ask the right questions and reply with a sensible first version.

Free first conversation · No obligation · NDA on request