Process
How an idea becomes a running system.
Here's how a project with us usually runs, step by step. We work out together what that looks like for your project.
01
Getting to know each other
We take time to talk through your project. It's about whether we're a fit and what's realistic.
- Understand the starting point and the goal
- Where possible, a rough idea of effort and cost
- A first view of whether it can be done
02
Concept and quote
We describe what's to be built, sketch the solution and send you a quote.
- A description of the planned scope
- Where needed, a sketch of the technical setup
- A quote to base your decision on
03
Development
We build in stages, and you regularly see how things are coming along. If something changes along the way, we talk it through.
- Usually a test environment you can try out yourselves
- Progress updates at a pace that suits the project
- Change requests early rather than late
04
Go‑live
Now it goes into real use. Depending on the project, this involves hosting, domains, moving your data, training and documentation.
- Moving data, usually with a trial run
- A walkthrough for your team as needed
- Documentation to suit the project
05
Ongoing support
After go‑live you can still get in touch, for example about updates, extensions or if something does get stuck.
- Technical monitoring and security updates, if you want them
- Help with faults, within the agreed scope
- Further development as agreed
Principles
Four principles behind our work
They sound obvious. In practice they aren't.
- Scope first, price second
- Before we name a price, we want to understand what's to be built. That helps both sides avoid surprises.
- Direct lines
- There's usually one shared channel for everyone involved, a chat for example. That way questions can be settled without waiting for the next meeting.
- Visible progress
- We'd like you to see results along the way, not only at the end. Where it fits, there's a test environment you can try out.
- Talking new requests through
- If new requests come up along the way, we usually talk through first what they mean in effort and cost.
Common questions
Common questions before you start
Nothing. The intro call is free and with no obligation. We usually talk by video or phone. Afterwards you can judge better whether we're a good fit.
That depends on the size and length of the project. The payment terms are set out in the quote. If you have any preferences, for example because of your budget planning, mention them early.
Wanting changes during development is normal. What a change means for effort, cost and time depends on how far it departs from the agreed scope. We work that out together case by case. How changes are handled is set out in the quote.
Usually both sides. We check the technology, depending on the project also with automated tests. You check whether it's right for the way you work, usually in a separate test environment. It's best to agree together beforehand what counts as “done”.
Then get in touch with us. What applies in that case, for example on warranty, follows from the law and from what we agreed in the quote. Support beyond launch can be agreed on top.
Tell us what's slowing you down.
A short conversation, free and with no obligation. Together we look at whether and how your project could be done.
Reach us directlyinfo@tscodeworks.de
We'll get back to you as soon as we can