Service · Product & technical consulting
Product & technical consulting: the right decisions before you build.
A technical sounding board for founders, school administrators and product teams: what to build first, which technology makes sense, and which risks to test early.
The situation
Many products waste money early on, not because the code is bad, but because decisions were made too fast: features nobody uses, technology too heavy for the team, or a vendor that is hard to leave.
Sometimes what you need is not a build team but someone who can read vendor quotes, assess an architecture, or help shape a realistic first version.
Is it a fit?
A good fit for
- Non-technical founders who need to shape a first version and choose who builds it
- Teams with their own developers who want a second opinion
- Organisations comparing several vendor quotes and wanting to see them clearly
- Products about to enter the next stage: a mobile app, a new language, or payments
Not a good fit for
- You are looking for someone to sign off a decision already made
- You need legal, tax or investment advice
- The question can be answered by a single article: we will tell you so
What you get
- A summary of the problem, the users and the product goals
- The scope of the first version, including what is deliberately left for later
- Architecture and technology choices, with the reasons
- A list of risks and how to test them first
- A staged plan that any team can carry out
How it works
First conversation
You tell us about the product, the users and the decision you are facing. We agree which questions need answering.
Mapping
We read what already exists: documents, apps, vendor quotes or code. Follow-up questions come in writing.
Decision document
You receive a document setting out the options, reasons, risks and a staged plan.
Review session
We go through the document with your team, then update it if anything changes.
What you own at the end
- A written document you can take to any team or vendor
- A record of the reasoning behind each decision, so it can be revisited
- No obligation to continue building with us
Cost and time
Ad-hoc consulting is billed per hour. For a new product we suggest a 1–2 week Mapping Session (from IDR 12 million) that produces a written scope, risks and a cost estimate; its fee is credited to the project if you go on to build with us.
- From
- IDR 750,000/hour
- Estimated time
- Hourly · mapping 1–2 weeks
Common questions
Do we have to build with Candora afterwards?
No. The document is written so that any team can act on it, including your own team or another vendor.
Is it meetings or documents?
Both. We talk by chat or video call, and the outcome is always a written document.
Can you review quotes from other vendors?
Yes. We compare scope, technology, risks and what you own at the end, not just the price.
What about keeping our idea confidential?
A confidentiality agreement can be discussed before you share any details. We only ask for the access we actually need.