Contact

Describe the problem. We will tell you if it is a fit.

You do not need a requirements document, a fixed scope or a defined budget. Describe the situation and we will come back with an honest read, including when the answer is that we are not the right choice.

What helps in a first message

• What the problem is today. What is stuck, what is manual, what costs too much.
• What already exists. A system in use, a spreadsheet, or nothing yet.
• Who will use it. Internal team, end customers, the public.
• Whether there is a deadline that cannot move.

None of it is required. A three line message is a fine place to start.

What happens next

• First conversation. Understanding the actual problem, no commitment.
• Proposal. Scope, timeline and price in writing, with what is out of scope stated explicitly.
• Build. Partial deliveries you can already use, not one package at the end.
• Handover. In production, with the repository and documentation in your name.

Response time

Within 2 business days for proposals and project conversations.