The Foundry page invites chemists to "Send us your molecule" or "Discuss your experiments", but both buttons open an email, and so does every "Request a Demo" and "Contact Us" on the homepage. Meanwhile the Foundry API docs define exactly what a good brief looks like: Molecule (target, amount, purity), Reaction (scale per well, well limit, measurement goal) or Custom, and each estimate comes back with price, delivery dates and assumptions. An agent gets a structured intake and a status trail. A human gets a blank email and has to guess what to include, and b12 gets briefs that need another round of questions before anyone can quote. Rivals such as Enamine use a "Request a quote" form.
First action
Copy the Foundry API's Molecule, Reaction and Custom fields into a simple web form on /foundry/.
How to measure it
Quotable Foundry briefs (no follow-up questions needed)
- Now
- –
- Target
- 2x the current monthly email briefs
- By
- 60 days
Steps
Map the fields
Take the Molecule, Reaction and Custom fields from the Foundry API schema and mark which are required for a first estimate.
Co-Founder & CTO half a day
Build the form
A brief-type picker with conditional fields, structure upload or SMILES, deliverable choice and chemistry flags, on /foundry/.
Founding Product Engineer 2 days
Connect the pipeline
Write each submission as a Foundry request with the same statuses as the API, so web and agent briefs share one queue.
Co-Founder & CTO 1 day
Write the confirmation
Say what happens next, when an estimate is expected, and how confidential structures are handled.
Co-Founder & CEO 2 hours
Swap the buttons
Point "Send us your molecule", "Discuss your experiments" and "Request a Demo" at the form; keep email as a fallback link.
Founding Product Engineer 2 hours
Review every brief
A chemist checks each brief within one working day and notes which fields were missing.
Research Scientist ongoing
Measure
Compare briefs, quotes and acceptances with the last quarter of email enquiries.
Co-Founder & CEO monthly
Why it works
Put a short web form on /foundry/ built on the API's three brief types. A picker (molecule, reaction, custom) shows only the fields that brief needs: a SMILES or structure upload and the amount and purity for molecules; scale per well, well count and measurement goal for reactions; free text for custom work. Add optional fields for deadline, chemistry flags (air-sensitive, photochemical, high-pressure, which the Zurich lab already handles) and whether the customer wants compounds, data or both. Each submission becomes a Foundry request with the same statuses the API uses, and the submitter gets a confirmation saying what happens next and when to expect an estimate. Keep the email link as a fallback and add a note for confidential structures (NDA first). Use the same form for "Request a Demo", with a field that routes Foundry, Selenium, Palladium and Cobalt requests.
A structured brief removes the back-and-forth that slows every first quote, and it tells buyers what b12 needs and can do. Because the form writes into the pipeline the API already uses, it needs almost no new back-office work, and every enquiry becomes measurable: briefs submitted, briefs quoted, quotes accepted.
Ready to use
ChecklistFoundry brief form fields
[ ] Brief type: Molecule / Reaction / Custom [ ] Molecule: structure (SMILES or file) or code name under NDA, amount, purity [ ] Reaction: transformation, scale per well, number of wells, measurement goal [ ] Custom: mixing, dilution, sample preparation, input matrix [ ] Deliverable: compounds, data (including failed reactions), or both [ ] Chemistry flags: air-sensitive, photochemical, high-pressure [ ] Target date and budget range [ ] Work email and organisation [ ] Confirmation: what happens next and when the estimate arrives
Risks and how to handle them
Pharma teams won't paste structures into a web form
Allow a code name or "structure under NDA" option and start with the scope fields only.
More low-quality enquiries
Make amount, purity or scale required, and add a short budget-range field.
Evidence
- Your websiteFoundry page: "We make the molecules AI designs." Customers "Send us molecules or a chemistry workflow"; a partner HTE lab at the University of Zurich "runs Chemspeed workflows from solid dispensing to LC-MS analysis" and handles "air-sensitive, photochemical, and high-pressure chemistry"; "Our own Bay Area lab is next." The "Send us your molecule" and "Discuss your experiments" buttons open email; the page gives no prices, turnaround times or example projects.Source
- Your websiteFoundry API docs: a pilot that "requests quotes" and "does not accept orders, take payment or authorize lab execution"; one intake with three brief types: Molecule (target, requested amount and purity), Reaction (scale per well, well limit, measurement goal) and Custom (mixing, dilution, sample preparation); a published estimate "includes price, currency, delivery dates and assumptions"; request statuses received, in_review, on_hold and estimate_available; credentials are issued privately per customer.Source
- Your websiteHomepage (checked November 10, 2026): H1 "AI-Powered Chemical Synthesis"; Selenium ("2 vs 5 steps to target", "70% faster route design"), Palladium ("99% yield on first plate", ">80% conversion rate") and Cobalt (protocols "for Chemspeed, Opentrons, or other automation platforms"); "Request a Demo" and "Contact Us" are protected email links, with no form, booking or pricing link anywhere on the page; no customer logos or testimonials; "Built by researchers from Roche, Chemspeed, Max Planck Institute, and EPFL"; "Backed by Y Combinator"; SOC 2 Type 2.Source
- Competitor researchEnamine sells custom synthesis alongside "400 Thousand compounds in stock" and over 650 chemists, with a "Request a quote" form and a separate custom request page.Source