Proof of concept
Test whether a technical approach can do the required job before building the full application.
PLANNING RESOURCES
Before you commit
to the build.
Practical guidance for deciding what to test, what to build first and how to move forward.
THREE DIFFERENT QUESTIONS
Can the technology do it?
How will people use it?
Will users find it valuable?
PRODUCT PLANNING
PoC, prototype or MVP?
Prototype
Explore the proposed experience and get feedback on how people would use it.
Minimum viable product
Launch a focused working product so intended users can complete a task and help inform the next decision.
PROJECT PLANNING
Start with the uncertainty.
When does custom software fit?
Map the workflow and the gaps in existing tools. Compare configuration and integrations with a custom build. A new application is worth assessing where important business rules, access requirements or user tasks remain unmet.
Custom software developmentWhat affects cost and timing?
Workflows, roles, integrations, data migration, platform constraints and review arrangements shape the scope. Share these dependencies early so the proposed first release can be estimated meaningfully.
What should we prepare for a first discussion?
Describe the current process, the people involved, the tools you use and the change you want. Existing examples, screenshots or a short walkthrough can help explain the requirement.
START WITH A CONVERSATION
What would you like to build or improve?
Tell us what happens today, who needs to use the solution and what you want to change.