Shutdown data and what survivors do differently
Federal closure data for new businesses, how the first-year drop compares across opening years, and what the survivors measurably do differently.
Founder segments
Corporate innovators
Considerations for a person building a product out of an employer: who owns the work, what the agreements say and what to settle first.
WE is a long-horizon business incubation and consulting firm. WE makes no promise of funding.
If you work for an employer, the program’s own description of a good fit is on the page about who the program is for. If a question about your employment is not answered there, ask through the contact page.
Who this is for
You work for an employer and have a product idea that came out of that work, or sits close to it. Who owns what you have made, what your agreement says and what your employer thinks are questions to settle before anything else.
Common challenges
-
Knowing who owns what you have made
Ownership comes from three layers: statute, your employment agreement and the facts of how the work was made.
-
Reading your own agreement
Statute is the floor and your contract may add to it, so every document you signed, including the ones you have not read since, goes to your lawyer.
-
Telling an employer-backed spin-out from a departure
An employer-backed spin-out is a negotiation between two parties who both want it, while a departure with an idea starts from interests that are not aligned.
-
Selling to a larger organization
If your first customer is a large organization, expect more steps, such as procurement review, security questions and legal review.
Reading path
-
-
AI features and customer data: what to decide first
The decisions to make before customer data reaches a language model: what goes in, which account tier, how long it is kept, and what customers are told.
-
AI regulation for a small SaaS company: what to ask counsel about the EU AI Act and the Texas AI statute
Questions a small SaaS company can bring to counsel about the EU AI Act and the Texas AI statute, with dated facts from each primary source.
-
Climate-tech software: considerations before you build
Questions to settle before you build software for emissions data and climate reporting, from US federal, California and European Commission pages.
-
Customers as capital: pilots, prepayment and design partners
How pilots, prepayment and design partners can fund a first product, and the terms worth writing down before any of them starts.
-
Fintech SaaS: considerations before you build
Questions to settle before you build software that moves money or holds financial data in the United States, from public agency pages. Not legal advice.
-
Founders inside a company: intellectual property and employment agreements
If you start a company while employed, who owns what you build? Federal copyright and patent rules and one state statute, with questions for counsel.
-
Government software: considerations for selling to the public sector
Questions to settle before you build software for US government buyers: registration, commercial acquisition, FedRAMP, Section 508 and the ADA.
-
Healthtech SaaS: considerations before you build
Questions to settle before you build health software in the United States: business associates, the Security Rule, breach notice and FDA device software.
-
Hiring across borders: employees, contractors and employers of record
The three ways a company can engage someone in another country, what each changes, and the questions to bring to an adviser licensed where the person works.
-
HR and recruiting software: considerations before you build
Questions to settle before you build hiring software: automated tool audits, selection-rate rules, background checks and the EU AI Act, from public texts.
-
Human review in an AI feature: where to keep a person in the loop
Where a person should review an AI feature's output, how review fails when it becomes a rubber stamp, and what standards and laws say about oversight.
-
Insurance for a software startup: what exists and what to ask
The kinds of business insurance a US small-business agency lists, what regulators say on workers' compensation and cyber risk, and questions for an agent.
-
Platforms and ecosystems: when a product becomes a platform
How a software product turns into a platform that others build on, what that asks of your interfaces, permissions and partner support, and why it comes late.
-
Security software: considerations before you build
Questions to settle before you build security software: the frameworks buyers use, secure development, SOC 2 reports and the EU Cyber Resilience Act.
-
Spinning a product out of an employer: what to settle first
Questions to settle before a product built at an employer becomes your company: who owns the work, what your agreement says, and which laws differ by place.
-
The NIST AI Risk Management Framework for a small team
What the NIST AI Risk Management Framework contains, how its four functions read at the scale of a small team, and what the framework does not say.
-
Vertical SaaS: depth over breadth
What vertical SaaS is, how building for one industry changes the product, the sale and the rules you work under, and the trade-offs to weigh before you narrow.
Request the brief: Corporate spinouts
Read the open abstract first. The full brief arrives by email after you ask for it.