Seguridad
CONFIDENTIAL
Discovery for a native Android app and a monitoring console for in-transit cargo custody, with real-time GPS, OCR and offline mode.
- Kotlin
- Native Android
- Offline-first
- Low-coverage zones
- Signal Protocol
- E2EE chat
PXL DISCOVERY
Most requested
Serious discovery, before you invest.
We research the problem, the users, the market and the technical constraints to hand you an actionable product plan.
- 3 to 8 weeks
- Typical duration
- Team depends on scope
- Team
- PXL Project
- Model
What's included
A modular scope, set by the stage of the product.
Stakeholder interviews
1 to 1.5 hour sessions with the CEO, process owners, the technical team and current users, to map context, constraints and the real business metrics.
User research
Interviews with end users, on-site observation where it applies, and analysis of existing sources such as support tickets, NPS and sales conversations.
Competitive and market analysis
Benchmarking of direct and indirect competitors, analysis of pricing, positioning and unresolved points of friction in the market.
Process and flow mapping
Diagrams of current (as-is) and proposed (to-be) flows, identifying bottlenecks and measurable automation opportunities.
Information architecture
We structure content, modules and navigation around real use cases rather than internal org charts.
Navigable Figma prototype
Wireframes and/or a low or medium fidelity prototype to validate with users before writing a single line of code.
Roadmap and prioritised backlog
A phased plan with MVP, V1 and V2, priorities by impact and effort, and clear technical dependencies.
Estimate and investment plan
Investment ranges per phase, timeline hypotheses and contracting model options.
Who it's for
Is PXL Discovery what you need?
We'll help you decide quickly. If we are not the right match, we point you to who is.
This is not for you if…
- You already have the problem, the solution and the scope fully defined
- You need a quote in 48 hours without having talked about the real problem
- You are looking to validate an idea with no identifiable market yet
- The total budget cannot absorb a serious Discovery. In that case, consider:
- There is no business decision-maker committed to taking part in the sessions
This is for you if…
- You have a strategic initiative worth millions and cannot get the scope wrong
- The project involves several areas, legacy systems or complex integrations
- You have tried to build the product before and it never reached production
- You need to align a committee or board before approving investment
- Your internal team has the business knowledge but not the product methodology
Problem
What it costs to build without Discovery.
The most expensive mistake in software is not writing the code badly. It is building the wrong thing. Many companies skip Discovery through calendar pressure, or because it looks like an optional cost. The result is predictable: scope that grows out of control, constant rework, demoralised teams and a final product nobody uses.
Teams building features that solve no real problem
Constant scope changes that double or triple the budget
Misaligned stakeholders who end up vetoing advanced deliveries
Products launched without research that have to be rewritten in 12 months
Technical decisions taken without understanding the business context
Outcomes
Discovery is not a cost. It is control.
A Discovery done properly is not a cost. It is the investment that decides whether the next 6 to 18 months of development generate real value or only technical debt. Companies that invest in Discovery close projects with 30 to 50% less budget drift and reach production 2 to 3 months earlier than those that skip this phase.
Reduced financial risk before committing large budgets
A clear scope, agreed between business, product and technology
An actionable roadmap that works for selling the investment internally
Technical decisions aligned with the real horizon for growth
Less rework, fewer surprises, fewer scope changes mid-project
Process
The 6 steps of a typical engagement.
Kickoff and alignment
A kickoff session with key stakeholders to define the objectives of the Discovery, the success metrics and who takes part. We agree the schedule of sessions.
Research
Interviews with stakeholders and users, observation of current processes, analysis of existing sources and competitive benchmarking.
Synthesis
Mapping of problems, opportunities, personas, user journeys and technical constraints. Identification of product hypotheses.
Definition and design
Information architecture, key flows, wireframes and a navigable Figma prototype to validate before building.
Validation with users
Usability testing of the prototype with 5 to 8 real users, to validate hypotheses and adjust before the roadmap.
Roadmap and investment plan
A final document with phases, a prioritised backlog, an investment estimate and a recommended contracting plan.
Related case studies
Projects where this service played the leading role.
Retail
CONFIDENTIAL
Discovery for a multi-vendor hardware marketplace with a Flutter app, customer, supplier and admin portals, and split payments.
- Flutter
- Cross-platform
- Conekta
- Split payments
- Vue.js
- 3 web portals
Fintech
CONFIDENTIAL
Discovery for a membership platform with automated payment dispersion, tax withholdings and CLABE account generation for partners.
- STP
- CLABE accounts
- Stripe
- Subscriptions
- CFDI
- SAT tax compliance
Stack | Tools | Standards
The tools we use on PXL Discovery.
Research methodologies with a scientific basis.
- Figma
- Dovetail
- Maze
- Loom
- Jira
- Miro
- Typeform
- UserTesting
- Amplitude
- Hotjar
Frequently asked questions
What almost everyone asks.
Why do I need a Discovery if I already know what I want?
What you ask for in the brief is usually the symptom, not the problem. Discovery validates whether the solution you have in mind is the right one and, in many cases, finds higher-impact opportunities with less effort. If after the Discovery we confirm your original hypothesis was right, we have saved you months of rework anyway.
What does a Discovery cost?
It's a fraction of the total project cost, meant to reduce the risk of the larger investment that comes after. It typically takes 3 to 8 weeks depending on the project, which is the main factor that determines cost. Reach out to us through Contact and we'll give you a real range for your case.
Is the Discovery deducted from development if I hire you?
Yes. The only condition is continuing development with us: if you do, the Discovery cost is deducted from the first phase.
Can I buy Discovery without committing to the development?
Yes. Discovery is an independent deliverable (a scope document, roadmap, and estimate) that you can use with us or with any other provider.
Who takes part from my side?
Ideally whoever knows the business problem (founder, product owner, or the user-facing area) and someone with technical vision if you already have an internal team. You don't need a full team, but you do need real availability during the 3 to 8 weeks.
What happens if after the Discovery we decide not to build?
You keep the roadmap and the estimate either way. We'd rather you decide not to build in time than build something that wasn't worth it.
Related services
These three are usually the natural continuation after a Discovery
PXL SOFTWARE
PXL Software
Enterprise platforms. Custom SaaS, ERPs, dashboards and APIs with production-grade engineering.
PXL EXPERIENCE
PXL Experience
UI/UX Design. Design based on behaviour and conversion, validated with real users.
PXL MVP
PXL MVP
Minimum viable products. Reaching the market in 8-12 weeks with enough to learn from, not to impress.
Before burning budget, validate.
A 30-minute call to see whether Discovery is what your initiative needs.