Contacts
Get in touch by email.
The address above is displayed as plain text. Please copy it into your email client. This site does not include a contact form.
The problem
Describe what is not working today or what the new system should make possible, in plain language. A short description of the current process is more useful than a feature list.
Users and roles
Who will use the system, how many people, and which tasks each role performs. Note whether it is internal, customer-facing, or both.
Existing systems
Any software the project must connect to or replace — accounting, CRM, ERP, payment providers, internal databases — and whether APIs or exports are available.
Constraints
Platform or hosting requirements, data residency or regulatory considerations, language requirements, and any technology choices already fixed.
First release
What the first usable version must contain, and what can wait. This is the fastest way to reach a realistic scope discussion.
Current state of work
Whether there is an existing codebase, designs, documentation or a previous vendor's deliverables that we should review.
Review
We read the description and identify what is clear, what is missing and which parts carry the most technical risk.
Questions
We reply with specific questions rather than a generic proposal, so the scope is based on your actual constraints.
Written scope
Once the requirements are clear, the outcome is a written scope with acceptance criteria and explicit non-goals.
Enquiries are handled in English. Please avoid sending confidential material in a first message; describe the context instead.