Godela's whole product starts with "upload simulation data", and the homepage pushes one action: "Request a Pilot", twice. Both buttons, and "Contact us", open a founder's personal calendar. Nothing on godela.ai says what a pilot includes, what data Godela needs, where that data is stored, where the models run, or who can see them. There is also no privacy policy, terms or security page (/privacy returns 404). For a hardware team, CAD and simulation results are core intellectual property. The engineer who wants the pilot has to get it past IT security and legal, and right now has nothing to forward to them.
First action
Write plain answers to five questions: where is uploaded data stored, who can access it, is it used for anything beyond the customer's model, how is it deleted, and where can the model run.
How to measure it
Pilot request to signed pilot rate
- Now
- –
- Target
- +30% versus the last quarter
- By
- 90 days
Steps
Answer the data questions
Storage, access, training use, deletion and deployment options, as true today.
CTO and Co-founder 2 days
Define the pilot
Scope, data needed, deliverables (validated model plus report), length and what happens after.
CEO and Co-founder 1 day
Write the page
A /pilot page with the scope, data list and data-handling answers.
CEO and Co-founder 2 days
Add the legal basics
A privacy policy and terms linked from the footer, reviewed by counsel.
CEO and Co-founder 1 week
Make the reviewer PDF
A one-page security and data summary to download.
CTO and Co-founder 1 day
Repoint the buttons
Both "Request a Pilot" buttons go to /pilot.
Founding Engineer (SWE) 1 hour
Track
Requests, security questions raised and time to signed pilot.
CEO and Co-founder monthly
Why it works
Publish a /pilot page and point every "Request a Pilot" button at it. It covers: (1) what a pilot is: one application, the team's existing runs (the homepage demo uses 2,400 simulations and 12 parameters), a validation report against held-out solver results, and a typical length; (2) what to send: file formats and how much data is enough; (3) data handling, written as plain answers: where data is stored, who can access it, whether it is used to train anything beyond the customer's own model, deletion on request, and options such as running in the customer's own cloud account if offered; (4) a one-page PDF version for security reviewers; (5) the pilot intake (idea 2). Link a short privacy policy and terms in the footer. Only state what is true today; where something is on the roadmap, say so.
The bottleneck in enterprise engineering pilots is rarely the engineer's interest; it is the internal review that follows. A page that answers the data question up front lets the champion forward one link instead of waiting on a questionnaire, and it reads as maturity next to rivals that show deployment partners. It also turns a generic calendar booking into a scoped request.
Ready to use
ChecklistPilot page checklist
[ ] What a pilot includes (one application, validation report, length) [ ] What to send: formats and minimum data [ ] Where data is stored and who can access it [ ] Whether data is used beyond the customer's own model [ ] Deletion on request [ ] Where the model can run [ ] Downloadable one-page summary for security reviewers [ ] Privacy policy and terms in the footer [ ] Both "Request a Pilot" buttons point here
Risks and how to handle them
Promising data controls that are not built yet
List only what is true today and label anything planned.
Too much detail scares off early-stage interest
Keep the page short and put detail in the PDF.
Evidence
- Your websiteHomepage (checked November 9, 2026): headline "Godela is the frontier of AI for the physical world."; a Train, Explore, Optimize flow (upload simulation data and Godela trains a physics-constrained model); applications: Data Center Thermals, Electronics Cooling, Aerodynamics, Electromagnetics, Structures and Build Your Own. The "Contact us" button and both "Request a Pilot" buttons open the same personal Calendly page of a founder; the only other links are [email protected], LinkedIn and the YC launch post. There is no privacy policy, terms, security or data-handling page, careers, docs, blog, case studies or pricing, and nothing on how uploaded CAD or simulation data is stored or where the models run.Source
- Your websiteSite structure (checked November 9, 2026): godela.ai is one page; /sitemap.xml, /robots.txt, /privacy and /careers return 404. Meta description: "Godela is bringing AI-powered physics intelligence to the physical world." The headline changed from "Godela" to "Godela is the frontier of AI for the physical world." after October 2025. No blog, newsletter, case studies, testimonials or video channel; LinkedIn is the only social profile. Domain registered February 2025.Source
- News coverageY Combinator launch post: Godela turns engineering questions into physics-informed models that are faster and cheaper than traditional simulation, positioned as a layer on top of existing simulations rather than a replacement; engineers can ask in natural language or upload CAD files, experimental results or simulation data. The problem it names: weeks or months of simulation and parameter tuning to answer one question, so many questions never get asked. Its asks: introductions to engineers with simulation bottlenecks and partnerships with engineering teams.Source
- Competitor researchRivals' own homepages: Neural Concept, an "AI-first engineering platform" with four named customer stories across automotive and aerospace and AWS, Microsoft and NVIDIA as deployment partners; PhysicsX, "Engineering. Reengineered.", serving five industries with a sailing-team case study and a "Talk to an engineer" button; Monolith, "Test less. Learn More.", claiming test plans cut by up to 70%, with testimonials from carmakers and aerospace firms, "Request a demo", and now part of CoreWeave.Source