How We Work Together
First, we find out whether the problem is worth solving
We don't need a technical brief from you — we'll propose the type of solution based on the problem. We care that the result is simple to run and that the customer keeps control of their own data and source code.
Send a problem for review-
1
Send us the problem
Tell us what's troubling you and attach supporting materials if useful.
-
2
We provide a short consultation free of charge
We'll discuss the problem on a short call, typically lasting up to 30 minutes. The goal is to understand your problem and processes and agree on a meaningful solution with you.
-
3
We prepare a detailed analysis
The analysis describes the current situation and provides a detailed solution proposal, often including a prototype. The prototype helps you picture the result more clearly. The analysis also includes a development quote and delivery timeline.
-
4
We deliver the solution
During development, we'll regularly discuss progress with you and refine the brief within the agreed scope. The handover also includes a practical walkthrough of how to run the tool, who uses it, and what's needed for day-to-day operation.
-
5
We handle fixes and adjustments
After handover, we provide a six-month warranty period during which we fix bugs against the agreed brief free of charge. Smaller adjustments can be arranged on an ongoing basis; larger changes, new directions, or changes to operations require a separate analysis.
-
6
We run the application
If you don't want to run the application yourself, we take care of its operation, security, and backups.
What we need from you
It mainly helps us to know:
- what exactly happens today
- who's involved in the process
- how often the work repeats
- roughly how much time it takes
- where mistakes or delays happen
- who can decide on the next step
What you can count on
You're looked after by experienced developers who:
- have practical experience in development, architecture, and real-world operations
- understand how your company runs, not just the technology
- assess whether a solution makes sense — before development even starts
- don't build a bigger solution than the situation calls for
Send us your problem
You don't need a finished spec. Just describe what your customer or your team has to handle manually today, where mistakes or delays happen, and which tool isn't working for you right now.
Send a problem for review