Look for product judgement
Ask candidates to challenge the brief. A strong partner should identify the main user outcome, the riskiest assumptions and the smallest useful release. A team that agrees with every requested feature may be optimising for project size rather than product success.
Request examples of decisions, not just screenshots. What was removed? Which assumption changed? How did user evidence alter the roadmap? These answers reveal how a team thinks when information is incomplete.
Examine production capability
A polished prototype is not evidence of reliable engineering. Discuss authentication, data protection, testing, deployment, observability, backups and incident response. If AI is involved, add evaluation, fallback behaviour and cost monitoring.
Clarify who owns architecture and technical documentation. The system should remain understandable beyond the individuals who first built it.
Evaluate the working model
Good collaboration has explicit decision rights, a visible backlog and frequent demonstrations of working software. Ask how scope changes are handled and how risks are communicated. Silence until a large milestone is rarely a sign of control.
Commercial models should support learning. A staged engagement with clear outcomes can be safer than a large fixed commitment based on uncertain requirements.
Check alignment after launch
Products need operation, measurement and iteration. Establish whether the partner can support the launch and how knowledge will transfer to an internal team. Define service levels only where they match genuine business risk.
Wishmakers builds and operates products of its own. That operating exposure informs decisions about reliability, payments, users and the less visible work required to keep a digital product useful.
Build what comes next
Turn the idea into a working system.
Wishmakers designs, builds and operates AI-native products, software systems and digital ventures across Europe, Morocco and Brazil.
Frequently asked questions
What should I prepare for a first meeting?
Bring the user problem, business objective, constraints, existing systems and any evidence from customers. A feature-complete brief is not required.
Should I choose a specialist or a generalist?
Choose the team whose relevant experience reduces your main risk. Domain insight may matter more than a specific framework.
How can I compare proposals?
Compare assumptions, exclusions, team composition, delivery method, ownership, post-launch support and total expected cost, not just the headline price.