Project enquiry
Describe the system you have and what needs to change.
Share the intended outcome, users, current workflow, constraints, and any fixed date. Douwyn will review it directly and respond with fit, missing information, and a practical next step.
A useful first brief
Information that helps an initial review
You do not need a finished specification. A concise description of these five points is enough to identify the important unknowns.
- Outcome
- The business or operational change the system should enable, not only a list of requested features.
- Users
- Who will use it, their roles, how often they work with it, and the environment they operate in.
- Current system
- The workflow, software, data sources, and manual steps already in place.
- Integrations and dependencies
- External services, vendors, access constraints, approvals, or systems the work depends on.
- Fixed date
- A launch, campaign, contractual, or compliance date—and which parts of that date are genuinely fixed.
What happens next
A practical response, not an automated sales sequence.
The first response is intended to establish whether the problem fits Douwyn’s scope and what should be clarified before anyone estimates implementation.
- 01
Review fit and scope
Douwyn reviews the outcome, operating context, dependencies, and likely risk areas.
- 02
Clarify the gaps
Missing information is resolved by email or a focused call when a live discussion is useful.
- 03
Recommend the next artefact
The next step may be a technical review, a scoped proposal, or a recommendation to take a different route.