1. Discovery
An exploratory conversation about the business problem, who is affected, current tools, constraints and what a successful outcome would look like. No pressure to invent a full specification on day one.
How we work
Complicated projects stay manageable when the path is clear. JDL keeps communication direct and the next step obvious from first conversation through long-term support.
An exploratory conversation about the business problem, who is affected, current tools, constraints and what a successful outcome would look like. No pressure to invent a full specification on day one.
JDL turns discovery notes into a clear scope: what will be built, what is out of bounds for now, and how delivery will be staged. You get enough detail to decide whether to proceed.
Key workflows are made visible early - screens, journeys and data shapes - so stakeholders can react while change is still inexpensive.
Build happens in stages with checkpoints. You see progress, raise edge cases from real operations, and keep the product aligned with the business.
Go-live is planned, not improvised. Hosting, access, content readiness and handover notes are handled so the system can be used with confidence.
After launch, JDL remains available for hosting, maintenance, fixes and sensible evolution. You keep a familiar point of contact rather than starting again with a new supplier.
It depends on the problem, the systems involved and how clear the starting point is - there is no honest one-size answer. JDL does not take on more work than can be given proper attention. Capacity stays focused so each project gets the time it deserves, rather than being rushed through a crowded pipeline.
JDL usually replies within one business day. The first conversation is exploratory: clarify the problem, outline options, and decide whether a scoped proposal makes sense.
Arrange an initial conversationExplore a similar project