An idea to test
You know what you would like to create, but not what to check before building. We clarify the problem, the people affected and the first useful test.
Product and technical mentoring for nontechnical founders
Decide what to build — and what to leave out.
An idea to test, a prototype to improve or a project losing focus? I help you compare your options before committing more time and money. A product decision session focuses on one specific question. You leave with a written summary of the choices, what still needs checking and the next actions.
- With Ludovic Chenneberg
- You build, I advise
- English / Français
Which decision is holding you back?
You do not need the technical vocabulary. Start with the choice you are unsure how to make.
A prototype to assess
Should you show it to users, rethink how it works or add features? We examine what it can already help you test and what you still need to choose the next step.
A project losing focus
The feature list keeps growing without making the next step clearer. We compare what to keep, simplify, postpone or stop.
Product decision session
One decision to make? Start with a focused session.
Choose the features for a first version, compare two tools or decide what comes after a prototype. Each engagement covers one question agreed together. Scope and fees are set out in a proposal before any session. You are not required to continue into ongoing mentoring.
- 01
Before the session, we agree on the question.
You describe the goal, what you have tried and the choice to make. We agree on the context to review, preparation, duration, format and fee, as well as the summary delivery timing and any follow-up.
- 02
During the session, we compare the options.
We examine realistic approaches, their trade-offs and the assumptions that could change the choice. I explain the product and technical implications in accessible language without taking over implementation.
- 03
After the session, you keep a written summary.
It records the options considered, the reasons for the choice or what needs checking before deciding, and the next actions. Use it to prepare your next test or continue the work with your developer.
Who you work with
Work directly with Ludovic Chenneberg.
I am a software developer and the founder of TechnoConception in Montréal, working across software engineering, SaaS architecture and applied AI. In this service, I bring that experience to your decisions without coding your product for you.
- Product
- Connect a feature to the need it serves and the test that could help evaluate it.
- Technical choices
- Understand the implications of a tool, architecture or scope decision.
- Direct advice
- Speak with the person examining your decision and explaining the trade-offs.
- Keep your own tools and developer. Mentoring does not require buying development services from TechnoConception.
- CetaSpace is my own product in development. Its published case study shows prelaunch engineering work, not results achieved by mentoring clients.
Illustrative example · Fictional situation
A summary you can use after the conversation.
This example shows the content of a decision summary. It is not a client engagement or an achieved result. Your session document addresses your question, the evidence available and the uncertainty that remains.
The question and context
Should online payments be added before testing a booking prototype? In this fictional example, the booking flow exists but has not yet been tried by its intended users.
The options compared
Integrate payments now; test booking without payment first; or simulate the payment step during a test. The first requires an integration, while the other options limit what can be learned about a real transaction.
The recommendation and why
If the immediate question is whether people can book the right service, test that flow before integrating payments. This keeps the trial focused on booking; it does not establish willingness to pay.
What could change the choice
If payment is essential to observing the commitment being tested, revisit the test and recommendation. The summary separates this assumption from the evidence already available.
The next actions
Prepare the booking scenario, observe where participants hesitate and record their feedback, then reconsider the need for payment. The founder carries out the tests; the advice helps interpret the findings and choose what follows.
For decisions across the project
Continue with a defined engagement when the need calls for it.
Product and technical mentoring helps you revisit decisions as you test and build. You can request this format directly. Before starting, we agree on the number and frequency of sessions, preparation and any support between meetings.
- Examine user feedback and what tests or the prototype actually allow you to conclude.
- Adjust priorities, compare tools and decide what to simplify or postpone.
- Keep a record of decisions, open questions and actions for you or your developer.
- Agree on a review point to continue, adjust or end the engagement, without implied renewal.
Advice for your project. Implementation stays in your hands.
You build with your tools or developer. Mentoring helps you choose and understand the trade-offs; it does not guarantee product success or commercial results.
What a focused session includes
- An agreed question and review of the context defined for it
- A comparison of options and their product and technical trade-offs
- A written summary of choices, assumptions and next actions
- Terms agreed before the session, including document delivery and any follow-up
What belongs outside mentoring
- Coding, implementation or delegated MVP delivery
- Debugging, code fixes or pair programming
- Code reviews and technical audits, which are separate services
- Security certification and operating the product in production
Questions to settle before you commit.
How much does a session cost, and how long does it take?
Duration, format and fees are set out in a proposal before any session, based on the question and agreed preparation. Submitting the form does not book a session or commit you to buying support.
What should I prepare?
For the initial inquiry, a few sentences about your goal, what you have tried and the choice holding you back are enough. A public prototype link is optional. You do not need a complete specification or presentation. We then agree on the context worth sharing for the session.
When will I receive the summary? Is follow-up included?
The written summary is part of the session. We agree on its delivery timing before starting, along with any clarification exchange or follow-up. Unlimited access between sessions is not implicitly included.
Can I book just one session?
Yes. A product decision session is a standalone engagement with no automatic commitment afterward. If several decisions need revisiting as the project develops, a defined mentoring engagement can be discussed. You can also request that support directly.
Do I need a company or a validated idea?
No. An early idea and a personal email address are welcome. We can start by identifying what to test with initial prospects. If you choose to build before validating, we make the assumptions and risks explicit so you can frame that choice.
What happens when there is not enough evidence to decide?
The summary identifies what is missing, why it could change the recommendation and which check could help. The next action may be a test or further research rather than a decision to build. The aim is not to offer certainty that the evidence cannot support.
What does this add to working with my developer or an AI tool?
Your developer and tools remain useful. The session sets aside defined time for your decision, constraints and realistic options, then leaves a written record of trade-offs and actions. It replaces neither implementation nor the evidence you need from users.
Can you review or fix my code?
Technical choices can be discussed during mentoring. Code reviews and technical audits are separate engagements. Programming, fixes, debugging and pair programming are not part of mentoring.
What information should I share through the form?
Describe the context without confidential code, passwords, access keys, sensitive documents or customer data. Inquiries are stored in TechnoConception’s private CRM and are not sent to an AI service. The privacy policy explains the processing. Arrangements for any confidential sharing should be agreed before those materials are sent.
Which decision would you like help with?
Describe your situation in a few sentences. You do not need a complete specification or presentation. The support format, organization and preferred timing are optional. Please leave out confidential or sensitive information.
Thank you. Your inquiry has been recorded and TechnoConception will respond directly.
The inquiry could not be recorded. Review the required fields and try again.
The security check was not accepted. Complete a new check and send again. Your message has not been sent.
Sending your inquiry…