Nocturlabe, the full simulation.
Two partners who want to sell an API that reads supplier invoices to accounting software vendors, and who have no clients yet. The case followed on this page, Nocturlabe's offering, from prototype to the first software vendor signing.
Two partners who want to sell an API that reads supplier invoices to accounting software vendors, and who have no clients yet.
An offering refined before the first meeting.
- Nocturlabe is the project of two partners from Toulouse. She is a developer, and he was a project manager at an accounting software vendor. Their API reads a supplier invoice, as an image or PDF, and extracts the data needed for accounting. They want to sell it to vendors, who would integrate it into their software.
- The prototype fits in a code notebook and a few test invoices. The partners have neither a prospect list nor proof that a vendor would pay.
- They hesitate between raising funds right away and waiting for a first client.
- In a few days, the prototype becomes an online demo and a page presenting the offer. Before any meeting, the offer goes before a panel of simulated buyers, agents built on profiles of product directors at accounting software vendors.
- The panel raises an objection the partners had not seen. With e-invoicing, invoices between businesses established in France will arrive with their data already structured, and the API will have nothing left to read there. The offering is refocused on invoices from suppliers established abroad, which mandatory e-invoicing does not cover, and on receipts attached to expense claims.
What remains with the partners
A simulated buyer never pays; real validation requires a vendor to sign and pay. The partners run every meeting themselves and set the price.
- Versions of the offer tested on the panel
- Meetings secured with software vendors
- Vendors engaged in a paid pilot
- Time between first contact and signing
The first meetings
The agent compiles a list of accounting and management software vendors, then prepares an outreach message for each based on what their software already does.
The partners send each message themselves and lead every meeting.
The paid pilot
The first software vendor to sign tests the API on its own invoices. The agent compares each reading against the entries made by its accountants and flags any discrepancies to the developer.
The partners agree the pilot pricing and success criteria with the software vendor.
Documentation and security
The agent drafts the API documentation and answers questions from the vendor's developers. It also prepares the security pack that software vendors require before going live, including European hosting.
The developer signs off every documentation page, and the data processing agreement is drafted with a lawyer.
Promotion
Once the first clients are onboarded, the agent publishes articles on foreign invoices and expense reports. It also responds to software vendors arriving via the website.
The partners review every article, and no client name is published without their consent.
Nocturlabe's offering, from prototype to the first software vendor signing
An offering, from prototype to the first signature.
- The prototype
- The API runs on the developer's computer, and no one else can try it.
- Within a few days, an online demo allows a software vendor to upload their own test invoices.
- First workstream
- The offering page
- The partners describe their project differently to each person they speak to.
- A page presents the offering, complete with the demo and frequently asked questions.
- First workstream
- The panel
- The partners are preparing to approach software vendors with an offering no buyer has seen yet.
- The offering is reviewed by a panel of simulated buyers, who each give their reasons for buying or not buying.
- First workstream
- The objection
- It would have arisen during the first meeting, in front of a real product director.
- The panel raises it beforehand. Invoices between companies established in France will arrive structured, and the offering refocuses on foreign invoices and expense receipts.
- First workstream
- Initial outreach
- The partners write to a few software vendors they know, then wait.
- The agent prepares the list of software vendors and a message for each, which the partners send themselves.
- Workstream 2
- The proof
- A software vendor expresses interest, without signing anything.
- The goal becomes a paid pilot, where the software vendor tests the API on their own invoices.
- Workstream 3
- Build the demo
- It puts the prototype online, with a space to upload test invoices.
- The developer validates each version.
- Write the page
- It writes the offering page based on the partners' notes.
- The partners validate every sentence.
- Assemble the panel
- It builds buyer profiles from public sources, such as job adverts and vendor product pages.
- Present the offering
- It presents the offering to each profile as it would be sold, including pricing.
- The partners set the tested price.
- Consolidate the reasons
- It collects the decision to buy or not with the rationale for each profile, then consolidates the reasons.
- Adjust the offering
- It proposes a new version of the offering based on the objections, then runs it past the panel again.
- The partners choose which version to sell.
- Prepare outreach
- It compiles the list of software vendors and drafts a message for each.
- The partners send each message themselves.
- Prepare for meetings
- Before each meeting, it summarises what is known about the software vendor and the likely objections.
- The partners conduct each meeting.
- The code repository
- The API and prototype code.
- Read access, and proposals reviewed by the developer
- Demo hosting
- A European server for the online demo.
- Deployment validated by the developer
- The simulated buyer panel
- Profiles and their reactions, version by version.
- Read and write
- The prospect list
- Targeted software vendors and communication history.
- Read and write
- The partners' email
- Outreach messages, sent by the partners.
- Drafts only
- The developer
- Builds the API and validates each version of the prototype.
- The commercial partner
- Leads meetings and negotiates with software vendors.
- Both partners
- Set the price and choose the version of the offering.
- The project's lawyer
- Drafts the data processing agreement offered to software vendors.
- The FDE
- Steers the engagement with the partners, from demo to proof. Responsible for each agent.
- Developer agent
- Puts the prototype online and prepares documentation.
- Panel agent
- Builds the simulated buyer panel and consolidates their reasons.
- Sales agent
- Prepares the list of software vendors and outreach messages.
- Control agent
- Verifies every claim on the page and in messages, flagging unsourced statements to the FDE.
- The panel loves the offering, and no software vendor signs.
- A simulated buyer never pays. The panel serves as a filter before meetings, and only a signature counts as proof.
- Model bias skews the panel.
- Profiles rely on public sources, and the partners review every objection before acting on it.
- The project raises funds too early.
- We focus first on getting a paying software vendor. The decision to raise funds rests with the partners.
- A software vendor's invoices are leaked.
- The demo runs on test invoices. The pilot runs on a server in Europe, with a signed data processing agreement.
- An outreach message is sent without review.
- The agent only writes drafts, and each partner sends their messages themselves.
- We start from the prototype and the partners' notes. Together with us, the developer details what the API can read and what it cannot read yet.
- The demo goes live, and the offering page follows. The offering is presented to the panel for the first time.
- Objections from the panel refocus the offering on foreign invoices and expense receipts. The new version is presented to the panel once more.
- The list of software vendors is ready, with a message for each. The partners decide with us on the order of the first meetings.
- Offering versions tested on the panel
- Versions presented to the panel, showing objections resolved from one version to the next.
- Meetings secured with software vendors
- Meetings held, relative to messages sent by the partners.
- Software vendors engaged in a paid pilot
- Software vendors that signed a pilot and settled its first invoice.
- Time from initial contact to signature
- Days between the first message to a software vendor and the signature of their pilot.