Problem definition
A clear description of the challenge, who it affects and why it matters.
A focused discovery and planning engagement
Know something isn’t working—but not what should change?
The Problem-to-Solution Blueprint helps you understand the real challenge, explore appropriate options and define a practical direction before committing time and money to the wrong solution.
Tell us what isn’t workingScope, timing and cost are confirmed only after we understand what the engagement requires.
IS THIS FOR YOU?
Clarity at the point between frustration and investment.
A Blueprint may be useful when:
- A manual process is wasting time or creating errors.
- Systems, spreadsheets or information do not connect.
- You have an app, AI or automation idea but need to understand whether it would create genuine value.
- You are unsure whether to improve, integrate or replace existing technology.
- Different people understand the problem differently.
- The business knows the result it wants but not the most appropriate way to achieve it.
WHAT THE BLUEPRINT MAY COVER
Useful clarity—not a generic report.
Every Blueprint is shaped around the situation, available information, people involved and decisions that need to be made.
The final scope may include some or all of the areas below. We agree the relevant outputs before the engagement begins.
Current-state understanding
A view of how the work happens now, including relevant friction, duplication, dependencies and gaps.
Opportunity assessment
An exploration of where process improvement, automation, AI, integration or better information could genuinely help.
Solution direction
A reasoned recommendation based on the need, users, constraints and desired result.
Priorities and next steps
Guidance on what may need attention first, what can wait and what should be explored further.
Decision support
A practical output designed to support an informed internal decision or a future design and development conversation.
HOW WE APPROACH IT
Understand first. Recommend second.
The exact process depends on the complexity of the situation, but the engagement generally follows three connected stages.
UNDERSTAND
Explore the reality
We listen to the people involved, review the available information and clarify the process, goals, dependencies and constraints.
MAKE SENSE
Find the real need
We examine the challenge, question assumptions, identify patterns and distinguish the underlying need from its visible symptoms.
SHAPE
Define a practical direction
We bring the findings together into an agreed output that explains the reasoning, appropriate options and recommended next decisions.
THE PURPOSE
The aim is to help you understand what is genuinely worth solving, where technology may help and what should happen next.
CLEAR EXPECTATIONS
The engagement may include
- An initial problem and context questionnaire
- Focused conversations with relevant people
- Review of appropriate process information
- Problem and opportunity analysis
- Exploration of realistic solution directions
- A documented recommendation or decision framework
- A final walkthrough and discussion
Separately scoped
- Detailed user-interface or software design
- Software, website or application development
- Large-scale technical, security or data audits
- Data cleansing, migration or systems integration
- Specialist legal, financial or regulatory advice
- Ongoing delivery or project management
If further design or development is appropriate, it is discussed and scoped separately. There is no obligation to continue into implementation with Make Sense Logic.
COMMON QUESTIONS
Before we begin.
How much does a Blueprint cost?
The cost depends on the complexity of the problem, number of people involved, information that needs to be reviewed and level of detail required. After an initial conversation, we will confirm the proposed scope and price before any work begins.
How long does it take?
Timing depends on the agreed scope, availability of relevant people and information, and the complexity of the situation. We will provide a realistic schedule after understanding what is required.
Do I need to know what technology I want?
No. The Blueprint is particularly useful when the problem or desired result is clearer than the solution.
What will you need from our organisation?
Usually, we need access to the people who understand the situation, honest information about what happens now and enough time for discovery, clarification and feedback. Exact requirements are agreed beforehand.
Is a Blueprint always the right first step?
No. Some problems are already sufficiently clear and may not need a separate discovery engagement. The initial conversation helps us decide whether a Blueprint would add genuine value.
Can Make Sense Logic build the recommended solution?
Potentially, where the work fits our capabilities and availability. Any design or implementation would be considered as a separate engagement, with its own scope, timing and cost.
What happens after I make an enquiry?
We review the information you provide and arrange an initial conversation where appropriate. That conversation helps both sides understand the situation and decide whether a Blueprint is a useful next step.
START WITH A CONVERSATION
Tell us what isn’t working.
You do not need a technical specification or a finished solution idea. Describe the situation in your own words and we will begin by understanding it.
An initial conversation can help establish:
- What is happening now
- Who the situation affects
- What you would like to improve
- Whether a Blueprint would be useful
- What an appropriate next step could be
Your enquiry will be submitted securely through the Make Sense Logic contact form.