No result found
This report needs a scored result to generate.
This is a static sample and does not depend on a scored result.
Back to the course page
PRAXORALAB Illustrative example · fictional venture, for format reference only
Validated Business Model Canvas
Ferrolytic Sensing Pte Ltd
Ferrolytic Sensing Pte Ltd's example venture: battery-free corrosion sensor patches for offshore steel infrastructure, monitored without a diver mobilisation or a planned shutdown. Every block below is validated against this one venture, brought into the room, not filled in from a generic template.
Nine-Block CanvasOffshore wind and oil & gas asset owners in Southeast Asia running steel structures past their ten-year inspection cycle, starting with one operator's flagship platform, not a multi-customer pilot.
Early corrosion-rate detection without a diver mobilisation or a planned shutdown, reporting a trend line instead of a single point-in-time reading.
Direct sales through the founder's existing marine-engineering contacts, plus a pilot-to-procurement path via Enterprise Singapore's Startup SG Tech grant network.
A dedicated pilot engineer embedded with the first operator for the first twelve months, moving to a subscription monitoring dashboard once the pilot is validated.
A per-patch hardware fee plus an annual data-subscription fee per monitored structure, not a one-time sensor sale.
The energy-harvesting circuit patent application, the founder's corrosion-signature training dataset, and a single contract manufacturer in Singapore.
Sensor calibration and data-model refinement, diver-free pilot deployment and retrieval logistics, and Enterprise Singapore grant reporting.
A contract manufacturer for the patch housing, a university materials-science lab for signature validation, and one anchor operator willing to co-develop the first pilot.
Dominated by sensor-grade piezoelectric material cost and calibration labour, not marketing; customer acquisition is currently one founder-led pilot at a time.
A nine-block canvas built around one anchor operator, rather than a spread of prospective logos, is the right instinct at this stage, and it is worth being specific about why. Most first-time founders fill the Customer Segments block with a market size and a list of companies that might buy. Ferrolytic instead names a single flagship platform belonging to one operator past its ten-year inspection cycle. That is a testable assumption, not a market slide, and it is exactly the kind of specificity this canvas exercise is built to force out of a founder before they have spent real money assuming the wrong thing.
The revenue model deserves equal scrutiny, and I would push back on it slightly rather than wave it through. Hardware fee plus an annual data subscription is the correct structure for a monitoring business, because the ongoing corrosion-rate trend line, not the one-time sensor, is what a plant engineer actually pays to keep. But nothing on this canvas states what happens to that subscription revenue if the operator's own maintenance budget cycle does not align with an annual invoice. I would want that answered before the second pilot, not discovered when the first renewal comes due.
Key Resources correctly names the training dataset and the energy-harvesting patent application as the two assets that matter, ahead of the physical patch itself, which is the right hierarchy for a deep-tech venture. What concerns me more is Key Partnerships: a single contract manufacturer in Singapore is a single point of failure sitting directly underneath a trade-secret manufacturing process, which the IP plan opposite depends on staying inside one NDA'd relationship. If that manufacturer becomes unavailable, Ferrolytic loses both its production capacity and the process knowledge in the same event, and nothing on this canvas names a second option.
The Cost Structure block's honesty is the block I would flag as most valuable, not least valuable, on this page. Stating plainly that customer acquisition is currently one founder-led pilot at a time, rather than inflating it into a repeatable go-to-market motion that does not exist yet, is exactly the kind of assumption this course exists to separate from the ones that are actually validated. A canvas that admits what has not been proven yet is more useful to a founder than one that reads well but is not yet true.
PRAXORALAB IP-Protection Plan
Every invention or asset behind Ferrolytic Sensing Pte Ltd's example venture, sorted into exactly one of three categories, patent, trade secret, or not yet decided, not left as a general policy statement.
Piezoelectric energy-harvesting circuit topology
Provisional patent filed in month one, before the first pilot conversation. This is the one subsystem a competitor could plausibly reverse-engineer from a torn-down patch, so it was the first claim drafted, ahead of anything else on this list.
Corrosion-signature training dataset and calibration weights
Kept as a trade secret rather than filed, since a patent application would require publishing the exact detection thresholds a competitor could copy directly, and the dataset keeps growing with every new pilot deployment.
Sensor calibration and manufacturing process
Kept as a trade secret and held inside a single contract manufacturer under NDA, since the process is difficult to reverse-engineer from the finished patch alone.
Corrosion-signature signal-processing algorithm
Not yet decided between a full patent filing and a trade-secret hold. Filing publishes the exact detection logic; not filing leaves the algorithm unprotected the day it first ships inside a customer's monitoring dashboard.
Sensor patch enclosure and subsea mounting mechanism
Not yet decided. A freedom-to-operate search against existing subsea sensor-housing patents has not started, so filing before that search would risk claiming ground someone else already holds.
Five items, three categories, and the sequencing across them is the part of this page I would spend the most time on in a real session, because the order these decisions get made in matters more than the decisions themselves. Filing the energy-harvesting circuit topology first, before the first pilot conversation, is exactly correct, and it is the one decision on this page I would not revisit. That circuit is the single subsystem a competitor could plausibly reverse-engineer from a torn-down patch sitting on someone else's structure, so it needed protection before it was ever physically exposed to a customer site.
The two trade-secret decisions, the training dataset and the manufacturing process, are defensible, but for different reasons that Ferrolytic's founder should be able to articulate separately if asked. The dataset is a trade secret because it is a moving target: it keeps growing with every pilot, and a patent claim would have to freeze a snapshot of thresholds a competitor could then design around. The manufacturing process is a trade secret because it is genuinely hard to reverse-engineer from the finished product alone, held inside one NDA'd manufacturer. If that second condition stops being true, that decision needs revisiting, not left on autopilot because it was correct in month one.
The two items marked "not yet decided" are where I would focus a real session's remaining time, because they are not equally urgent. The signal-processing algorithm's decision has a hard deadline attached to it that this page does not state explicitly: the day the algorithm first ships inside a customer-facing monitoring dashboard, it becomes observable, and any patent claim drafted after that point risks being invalidated by the venture's own prior disclosure. That is a decision Ferrolytic needs to make before Days 31–60 on the roadmap opposite, not during it.
The enclosure and mounting mechanism's "not yet decided" status is lower urgency but not zero, and I would correct one instinct I see often in founders at this stage: treating the freedom-to-operate search as a formality to run once funding closes. Filing, or building manufacturing tooling, around a mechanical design before that search runs is how a well-funded startup discovers eighteen months in that someone else already holds the exact housing geometry they built a supply chain around.
Ferrolytic Sensing Pte Ltd and its inventions are invented for this sample only, to show the shape of the output, not a real client's actual IP position. In the session, this plan is built from the venture a participant brings, not assigned from a template.
PRAXORALAB Go-to-Market and Funding Brief
The four questions a term sheet or grant reviewer will actually ask, answered for Ferrolytic Sensing Pte Ltd's example venture above, not left as an abstract framework.
Ferrolytic is entering through a single anchor operator's flagship platform, not a multi-customer pilot spread thin across several accounts. The offshore wind and oil & gas operators targeted next all share one property: steel structures already past their ten-year inspection cycle, where a diver-free reading is worth paying for immediately rather than after a long evaluation.
Both check the same thing before anything else: is there one paying (or grant-committed) customer, or only interested conversations. Ferrolytic's answer is a signed pilot agreement with the anchor operator, not a letter of intent, which is the specific evidence a Startup SG Tech reviewer and a seed investor both ask for first.
The Startup SG Tech grant is sequenced first, to fund the pilot deployment and generate the first real corrosion-signature dataset, before approaching a seed round. Raising seed capital before that dataset exists would price the round against a hardware idea instead of a working pilot with real data behind it.
The go-to-market brief deliberately does not promise investors a filed patent on the signal-processing algorithm, since that decision is still open on the IP-protection plan opposite. Overstating the IP position to close a round faster is the fastest way to lose credibility with a technical investor during diligence.
The choice to enter through one anchor operator's flagship platform, named specifically rather than described as a target segment, is the same discipline carried over correctly from the business model canvas, and it is why this brief reads as fundable rather than aspirational. What I want to correct is the assumption buried in the second answer, about what a term sheet or grant reviewer checks first. A signed pilot agreement is necessary, but it is not sufficient on its own, because both a grant reviewer and a seed investor will also ask what happens if that one anchor operator walks away mid-pilot. This brief does not yet name a second prospective operator waiting in the wings, and I would not let a founder skip that question in the room.
Sequencing the Startup SG Tech grant before the seed round is the correct order, and it is worth stating plainly why, since founders often want to raise seed capital first because it is a larger, faster-feeling number. A seed round raised before the pilot dataset exists prices the company against a hardware idea and a founder's credibility alone. The same round raised after a working pilot and a real corrosion-rate trend line prices the company against evidence, and that difference in valuation basis is usually worth more than the time saved by raising earlier.
The fourth answer, about not overstating the IP position to close the round faster, is the one I would defend most strongly to a founder who wants to soften it before sending this brief to an investor. A technical investor's diligence process will ask, directly, whether the signal-processing algorithm is patented, and "we are deciding between filing and trade secret, and here is our reasoning" is a materially stronger answer than a vague implication of protection that does not survive a follow-up question. I have watched a promising round stall for exactly this reason: a founder who oversold an IP position that unravelled the moment a diligence call asked a direct, specific question about it.
What this brief gets right, overall, is refusing to let the funding narrative run ahead of what is actually true on the ground. That restraint is rarer than it should be at this stage, and it is the reason I would tell an investor this venture is further along than its funding stage suggests.
PRAXORALAB 90-Day Venture Roadmap
The canvas, IP-protection plan and go-to-market brief above, brought together into one sequenced plan, ordered by what each phase's output makes possible next.
- Finalise the pilot agreement with the anchor operator, including data-ownership terms for the training dataset.
- File the provisional patent on the energy-harvesting circuit topology before any pilot hardware leaves the lab.
- Submit the Startup SG Tech grant application, scoped to the first pilot deployment only.
- Deploy the first patch on the anchor operator's structure and begin collecting real corrosion-signature data.
- Start the freedom-to-operate search for the enclosure and subsea mounting mechanism.
- Decide, with patent counsel, whether the signal-processing algorithm is filed or held as a trade secret.
- Convert the pilot's first corrosion-rate trend line into the go-to-market brief's core proof point.
- Open the seed conversation, positioned against a working pilot and a resolved IP-protection plan, not a hardware idea alone.
- Draft the subscription-dashboard terms for the second operator, based on what the first pilot actually required.
Foundation, then validation, then commercial readiness, and not any other order, because each phase's output is the input the next phase cannot proceed without. Filing the circuit patent inside Days 1–30, before any pilot hardware leaves the lab, is correctly sequenced ahead of deployment for the same reason it was correct on the IP-protection plan itself: the patch is unprotected the moment it is physically exposed on someone else's structure, so the filing has to land before, not during, the first deployment. Submitting the grant application in the same thirty days, scoped only to the pilot rather than the whole venture, is the right level of ambition for a first application; a grant reviewer trusts a narrowly scoped ask more than a broad one from a venture with no deployed hardware yet.
Days 31–60 is where I would apply the most pressure in a real session, because it contains the one item most likely to get quietly deferred: deciding, with patent counsel, whether the signal-processing algorithm is filed or held as a trade secret. Everything else in this phase produces a visible artefact, a deployed patch, a started search, that looks like progress on a status update. A counsel conversation that ends in a decision does not look like progress the same way, which is exactly why it is the item most at risk of sliding into Days 61–90 under time pressure, at which point the dashboard may already be shipping and the decision window may already be closing.
Days 61–90 is honestly sequenced, and I want to name why that matters: it opens the seed conversation only after the pilot has produced a real trend line and the IP decision from the previous phase is resolved, not before. A founder eager to raise capital is often tempted to start investor conversations the moment a pilot begins, rather than once it has produced evidence. Waiting the extra thirty days here is not caution for its own sake; it is the difference between raising against a working pilot with a resolved IP position and raising against a story that is still missing its two most important facts.
What "done" looks like at the end of ninety days is not a signed term sheet. It is a Ferrolytic that can answer, without a caveat, whether its core algorithm is patented or held as a trade secret, backed by a real corrosion-rate trend line from one operator's structure. That is a materially more fundable position than the one this canvas and this brief describe today, and it is reachable in the window this roadmap sets out, provided the counsel conversation in Days 31–60 does not slip.
Every figure, quote and decision on these four pages is invented for Ferrolytic Sensing Pte Ltd, a fictional venture, so the format of what a participant leaves with can be judged before enquiring. It is not a real client's deliverable, and no venture named Ferrolytic Sensing Pte Ltd is a Praxora Lab client. The session itself validates your own venture or technology idea, in the room, on the day.
Four hours, one session, facilitated by Patrick Ng.