Dream
Decide what to build, and whether to build it, before any code exists.
Resources
Insights
Practical, sourced pieces on how a SaaS idea becomes a company. Written by World Enterprise Editorial.
The desks at a glance
- Dream 7 articles
- Build 11 articles
- Grow 6 articles
- Fundable 8 articles
- Starting out 14 articles
- Funding and capital 13 articles
- Legal and company basics 8 articles
- Team and hiring 9 articles
- AI-native building 9 articles
- Go-to-market 10 articles
- Pathways 12 articles
- Business models 8 articles
- Sectors 8 articles
- Operations and wellbeing 11 articles
Show the figures as a table
| Desk | Articles |
|---|---|
| Dream | 7 |
| Build | 11 |
| Grow | 6 |
| Fundable | 8 |
| Starting out | 14 |
| Funding and capital | 13 |
| Legal and company basics | 8 |
| Team and hiring | 9 |
| AI-native building | 9 |
| Go-to-market | 10 |
| Pathways | 12 |
| Business models | 8 |
| Sectors | 8 |
| Operations and wellbeing | 11 |
Illustration: World Enterprise Group Incorporated, drawn at build time from the articles published on this site.
Written for the long clock
The desks follow a company over years, because that is how long a company takes.
51.4% 1
were still operating after five years
34.7% 2
were still operating after ten years
69.5% 3
of businesses that reach five years also reach ten
- U.S. Bureau of Labor Statistics, Business Employment Dynamics, Table 7 , Opened in the year to March 2020
- U.S. Bureau of Labor Statistics, Business Employment Dynamics, Table 7 , Opened in the year to March 2015
- SBA Office of Advocacy, Frequently Asked Questions About Small Business (2026) , 1994 to 2022 average
These figures describe all new U.S. businesses, not WE's results.
Every piece here is written by World Enterprise Editorial, the accountable byline for this site, and is meant to be used rather than admired. Each one names its sources, says what it cannot establish, and avoids statistics it cannot trace to a public document. Nothing here is a promise of funding, and nothing on legal or financial topics is advice.
The articles are grouped into desks. Dream covers deciding what to build, Build covers scoping and running a team, Grow covers the first customers and Fundable covers the evidence an investor will test.
The other desks cover the rest of what founders ask. Starting out is for the founder who is deciding where to begin. Funding and capital explains the money a company can raise or borrow. Legal and company basics covers the company, equity, IP and privacy, and is not legal advice. Team and hiring is about running a small team, in-house or remote. AI-native building is for a product that depends on a model. Go-to-market covers positioning, pricing and reaching the first customers. Pathways sets the routes into a company beside the routes to capital. Business models covers how B2B SaaS, vertical SaaS, marketplaces, platforms and developer products work. Sectors covers building software in fintech, healthtech, edtech and climate tech. Operations and wellbeing is about running the company and looking after the founder, without advice.
The desks
Each desk is a galaxy of sourced articles on one part of building a company.
-
-
Build
Scope, staff and ship a first release without over-building.
-
Grow
Win the first customers and keep them.
-
Fundable
Prepare evidence that survives diligence. No promise of funding.
-
Starting out
Where you begin depends on who you are: first-time, technical, non-technical, solo, student, second-career, corporate and global founders.
-
Funding and capital
Understand the money you can raise or borrow, before you ask for it.
-
Legal and company basics
The company, equity, IP and privacy basics to ask your counsel about. Not legal advice.
-
Team and hiring
Hire, onboard and run a small team, in-house or remote.
-
AI-native building
Build and operate a product that depends on a model, with the risks stated.
-
Go-to-market
Position, price and reach your first customers.
-
Pathways
The routes into a company and the routes to capital, side by side.
-
Business models
How B2B SaaS, vertical SaaS, marketplaces, platforms and developer products work, and what each asks of a first company.
-
Sectors
Considerations for building software in fintech, healthtech, edtech and climate tech. General information, not a claim of experience.
-
Operations and wellbeing
Run the company and look after the founder, in general terms and without advice.
Dream
Decide what to build, and whether to build it, before any code exists.
-
dream
Fake-door and concierge tests
Two ways to learn whether people will act before you build: a page for a feature that does not exist, and a service you deliver by hand. With an honesty note.
-
dream
Kill criteria: deciding in advance when to stop
How to write down, before you start, the evidence that would make you stop, change direction or continue, and why that decision belongs to your calmer self.
-
dream
Mapping the alternatives a customer already uses
A method for listing everything a customer does today instead of buying your product, from spreadsheets to doing nothing, and reading the gaps honestly.
-
dream
Bottom-up market sizing for a first SaaS
Size a market from countable customers and a defensible price, using public business counts and explicit assumptions instead of a borrowed top-down figure.
-
dream
Customer discovery interviews without false positives
Run customer interviews that surface real behavior and commitment instead of polite encouragement, with a question set and a way to log what you hear.
-
dream
Is your SaaS idea a business or a feature?
Six tests to run before you build, to find out whether your idea can stand alone as a company or only works as a capability inside someone else's product.
-
dream
Write the problem brief before the code
A one-page problem brief makes a team agree on who has the problem, what it costs and what done looks like before design or engineering begins.
Build
Scope, staff and ship a first release without over-building.
-
build
A boring first technology stack
How to choose a first technology stack for a SaaS product by asking about people, documentation and reversibility, with three technologies named as examples.
-
build
Estimating a first release: ranges and what they hide
Why one number misleads, how a three-point range works with an invented example, and what even a good range hides from you and from the people you tell.
-
build
Observability for a small team: logs, metrics and alerts you will actually read
A starting set of logs, metrics and alerts for a two- or three-person SaaS team, built on four signals and one rule: every alert must be one you can act on.
-
build
Product management for a first SaaS: roles, backlog and decisions
What product management is in a company of one to three people: three jobs, two ways to keep a backlog, and a decision log that outlasts memory.
-
build
Shipping safely with feature flags and rollback
How feature flags separate deploying code from releasing a feature, what rollback can and cannot undo, and why every flag needs a removal date.
-
build
Writing a product requirements document people read
A short structure for a product requirements document that engineers and teammates actually open, with an invented, labelled example you can adapt.
-
build
An operating rhythm for a remote offshore team
A weekly and daily rhythm for working with a team in another time zone: written handoffs, a short overlap, a visible plan and four-hour focus blocks.
-
build
Architecture decisions to defer in the first six months
Which technical decisions a young SaaS team can safely postpone, which must be made early because they are costly to reverse, and how to record both.
-
build
Build versus buy for auth, billing and email
How to decide whether to build or buy sign-in, billing and email in a first SaaS product, with criteria, the standards that apply and the traps to check.
-
build
Cutting an MVP with the cut-line test
A simple test for deciding which features belong in a first release, by drawing a line and asking what the customer cannot complete the core job without.
-
build
What a dedicated team is, and is not
What a dedicated team is: who steers the work, how it differs from freelancers and agencies, and what the arrangement does not cover.
Grow
Win the first customers and keep them.
-
grow
Feedback loops that reach the product
How a small SaaS team can collect customer feedback, sort it and turn it into product decisions, with a weekly routine that needs no research staff.
-
grow
Retention basics for a first SaaS
What retention measures in a subscription business, how to calculate customer and revenue retention with a handful of accounts, and what to do with the result.
-
grow
Onboarding is acquisition: time to first value
Why the first session decides whether a signup becomes a customer, how to define the first value moment, and how to remove steps between signup and that moment.
-
grow
Pricing page fundamentals for a first SaaS
How to build a clear pricing page for a first SaaS product - choosing a pricing model, stating what is included, and making the page readable and accessible.
-
grow
Support at five customers, not fifty
How to run customer support with a handful of customers: one inbox, a written log, and a weekly review that turns each question into a product decision.
-
grow
Your first ten customers: a founder-led sequence
A five-step sequence for winning the first ten paying customers by hand, with the founder selling and a log that turns each conversation into learning.
Fundable
Prepare evidence that survives diligence. No promise of funding.
-
fundable
Answering a security and privacy questionnaire
What the CAIQ, CCM, OWASP ASVS and NIST frameworks are, how a questionnaire answer relates to evidence, and the questions to bring to counsel.
-
fundable
Customer evidence and reference calls
What records show a customer relationship, what a reference call is, and what the FTC endorsement guides and review rule say when a customer's words go public.
-
fundable
Ordering a pre-seed evidence pack
How to arrange the records behind a founder's claims into one indexed set, in data room folder order, and what to ask counsel.
-
fundable
Choosing the right first investors for a SaaS company
How a founder can judge investor fit for a first SaaS company - the criteria worth writing down, questions to ask, and what to check before accepting money.
-
fundable
Evidence over narrative: what diligence actually tests
What due diligence checks in an early-stage software company, how it separates claims from evidence, and how to prepare records that stand up to questions.
-
fundable
IP, contracts and access diligence for small engineering teams
The ownership, contract and access records a small software team should keep in order, and why they matter to a reviewer. General education, not legal advice.
-
fundable
Questions to ask your counsel before you sign
A founder's list of questions to bring to your own lawyer before signing an investment, contractor or customer agreement. General education, not legal advice.
-
fundable
The founder time budget of a raise
How to plan the founder time that raising outside money consumes, what to protect, what to delegate and how to set a stopping rule before you start.
Starting out
Where you begin depends on who you are: first-time, technical, non-technical, solo, student, second-career, corporate and global founders.
-
starting
Encore founders: starting a company after fifty
What Census Bureau research says about founder age, prior industry experience and prior business ownership, and what a founder past fifty can plan around.
-
starting
Founder age and growth: what the Census study of 2.7 million founders found
Mean founder age rises with how fast firms grow. What a Census Bureau study of 2.7 million founders measured, and what it cannot say about one founder.
-
starting
From first filing to first payroll: what the timing data says
How many business filings become employers, and what a panel of 2004 startups earned by year eight. The public data on timing, and where it runs out.
-
starting
Women and immigrant founders: what the Census and research data show
Census Bureau counts of women-owned and minority-owned firms, and peer-reviewed research on immigrant entrepreneurship, with the limits of each source.
-
starting
A non-technical founder building SaaS: what to own and what to delegate
If you cannot write the code yourself, the decisions, accounts and records to keep in your own hands, and the work you can hand to a technical team.
-
starting
A technical founder's blind spots: selling, pricing and saying no
Three kinds of work a builder can overlook when starting a SaaS company: selling before building, setting a price on purpose, and keeping an explicit no list.
-
starting
Choosing a co-founder, or deciding not to
A co-founder is one way to cover missing skills, and the only one that makes someone an owner. How to list the work, test the fit and write things down.
-
starting
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.
-
starting
Founding from outside the United States: what changes for a remote founder
Where you live, where the company is formed and where customers are can be three different places. Delaware, UK and EU VAT examples, with questions for counsel.
-
starting
Part-time to full-time: deciding when to commit
Moving from a side project to a full commitment is a staged decision. How to write the criteria in advance, and what to leave to your own professionals.
-
starting
Second-career founders: turning domain knowledge into a SaaS idea
Years in an industry give you a problem others cannot see. How to separate what you know from what you assume, and turn it into a testable SaaS idea.
-
starting
Solo founders: where a second pair of eyes comes from
A solo founder makes every decision alone. Four sources of outside review, and a short session format borrowed from public-service assessments.
-
starting
Student founders: the questions to settle before you start
Before you build a company while enrolled, find out what your school's policy says about ownership. Two real policies compared, and the questions to ask.
-
starting
What a first-time founder should settle first
A checklist of decisions a first-time SaaS founder can settle early: the problem, the owners, the legal form, who owns the code, and who reviews your work.
Funding and capital
Understand the money you can raise or borrow, before you ask for it.
-
funding
Bootstrapping versus raising over a ten-year horizon
Most new firms start with little outside money. What Kauffman Firm Survey and federal survival data say about funding choices when the horizon is ten years.
-
funding
SBIR and STTR as patient capital for research-based companies
How federal SBIR and STTR awards fund research over years without taking shares, what the 2026 reauthorization changed, and what to ask first.
-
funding
The time between funding rounds: what Carta data reports
Carta reports that the median wait between rounds has stretched past 600 days. The figures, who they cover, and how to turn them into a runway question.
-
funding
Angels, micro-funds and funds: what the rules say and what to ask
Founders talk about angels, micro-funds and funds as different investors. This article sets out what US securities rules say about each and what to ask.
-
funding
Cap table basics for founders
What a capitalization table records, how options, the option pool and unconverted SAFEs appear in it, and what to ask your counsel before you sign.
-
funding
Crowdfunding and Regulation CF for a software company
What Regulation Crowdfunding requires of a company that sells shares online: who is eligible, the limits, the filings, and what to ask your counsel first.
-
funding
Funding a first SaaS from customer revenue
How customer payments can fund a first SaaS, what billing choices do to the timing of cash, what you owe for prepaid service, and the arithmetic to track it.
-
funding
Funding a software startup: the routes and what each asks of you
A plain-language map of the routes to money for a software startup, from customer revenue to grants, loans, investment and crowdfunding, and what each asks.
-
funding
Grants and SBIR programs for software companies
What the US SBIR and STTR programs are, who can apply, how the phases work, and what a software company should check before it writes a proposal.
-
funding
Reading a term sheet, line by line
A walk through the sections of a published model term sheet for a priced round, what each part is for, and the questions to ask your own counsel about it.
-
funding
Revenue-based financing and venture debt: when they apply
What public sources say about sales-based financing, loans and debt beside equity, and what to ask a provider before you agree to repay money from revenue.
-
funding
Runway and burn: the arithmetic
How to work out burn and runway with one worked example, what the arithmetic hides, and how to read the result before a decision about spending or raising.
-
funding
SAFE or convertible note: how the two instruments differ
How a SAFE and a convertible note differ, from debt and interest to what happens on a sale, with the questions to bring to your own counsel.
Legal and company basics
The company, equity, IP and privacy basics to ask your counsel about. Not legal advice.
-
legal
Choosing an entity: LLC or C corporation
What an LLC and a C corporation are, how each is created and taxed in the United States, and the questions to bring to counsel and a tax professional.
-
legal
Founder equity splits and vesting
How founder shares are issued, what vesting is and how a repurchase condition works, with questions for counsel. It gives no recommended split.
-
legal
Founder IP assignment and confidentiality agreements
Who owns code and inventions made by founders, and what the copyright, patent and trade secret statutes say about assignment and confidentiality.
-
legal
Open-source licenses inside a commercial product
What the MIT, Apache 2.0, GPL and AGPL license texts say about copying, shipping and offering software, and the questions to bring to counsel.
-
legal
Privacy law basics for a small product
What the GDPR, the CCPA, the COPPA Rule and the FTC Act say about personal data, from the primary sources, with questions to bring to counsel.
-
legal
Terms of service and privacy policy: what each document is for
A terms of service is a contract and a privacy policy is a notice. What the primary sources say about each, and the questions to bring to counsel.
-
legal
The 83(b) election and its deadline
What the 83(b) election is, what the statute and the IRS say about its 30-day deadline and how it is filed, and the questions to bring to a tax professional.
-
legal
Trademark name clearance before you commit
What the USPTO and the federal trademark statute say about similar marks, clearance searches and likelihood of confusion, with questions for an attorney.
Team and hiring
Hire, onboard and run a small team, in-house or remote.
-
team
Contractors and employees: the classification tests
How US tax and wage agencies, California and the UK decide whether a worker is an employee or a contractor, and what to bring to your own counsel.
-
team
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.
-
team
Offer letters: what they should state
What an offer letter is, the terms it usually states and what at-will means in the United States, plus questions to put to your own counsel before you send.
-
team
Onboarding a new team member: what to prepare before day one
A founder's preparation list for a new hire: access, equipment, paperwork, first tasks and people, with examples of the legal paperwork in the US and the UK.
-
team
Stock options for early employees: what an option is and what to ask
What a stock option is, how US tax sources describe the two main types, and the questions an early employee or a founder can bring to counsel before a grant.
-
team
Structured interviews for a small team
What a structured interview is, as a US federal personnel agency describes it, and how a small team can build one: shared questions, anchors and scoring.
-
team
Writing a job description people can answer
How to write a job description that a candidate can answer: outcomes before tasks, plain words, essential duties and advertising wording to check.
-
team
Writing down how a remote team works: a team handbook
What to put in a short handbook for a remote team: hours, channels, decisions, devices and time off, with public guidance on security and flexible working.
-
team
Your first hire: what to settle before you write the job
A decision framework for a founder's first hire: the work, the working arrangement, the money, the equity question and how you will judge the result.
AI-native building
Build and operate a product that depends on a model, with the risks stated.
-
ai
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
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.
-
ai
Choosing a model provider: the questions that matter
Questions to put to any language model provider before you build on it, drawn from vendor documentation on data use, retirement notice, limits and terms.
-
ai
Evaluating an LLM feature before you ship it
A method for testing a language model feature before launch: written success criteria, a test set with edge cases, grading choices and re-runs after changes.
-
ai
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.
-
ai
Metering and budgeting model usage
How to measure language model usage per feature and per customer, set limits before a bill surprises you, and handle the errors that limits produce.
-
ai
Prompt injection and the OWASP Top 10 for LLM applications
What prompt injection is, how the OWASP Top 10 for LLM applications describes it, and the design questions the list raises for a small SaaS team.
-
ai
Retrieval-augmented generation: what it is and where it breaks
What retrieval-augmented generation is, where it commonly fails in a product, and how to test retrieval and answers separately before launch.
-
ai
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.
Go-to-market
Position, price and reach your first customers.
-
gtm
A one-page positioning statement
A five-part method for writing down who your product is for, what it replaces and why it differs, with an invented example and a three-buyer test.
-
gtm
Choosing your first channels
Pick one or two places to look for first customers: start from the buyer, score what each channel asks of you and write each test down before you run it.
-
gtm
Cold outreach that follows CAN-SPAM
What the U.S. CAN-SPAM Act and the FTC compliance guide say about commercial email, quoted from the sources, with questions to bring to counsel.
-
gtm
Customer references and case studies without breaking FTC rules
What the FTC Endorsement Guides say about customer quotes, case studies and connections to customers, quoted from the rules, with questions to take to counsel.
-
gtm
Founder-led sales calls: a structure
A six-part structure for a first sales call run by a technical founder, a note template, and what the U.S. wiretap statute says about recording.
-
gtm
Landing page tests you can read
How a technical founder can plan and read a two-version landing page test using the NIST statistics handbook, with invented numbers and no benchmarks.
-
gtm
Marketplaces and partner channels: when a listing helps
How a technical or remote founder can read marketplace documentation to judge whether a listing helps, with each platform's rules attributed, none ranked.
-
gtm
Pricing a first SaaS: value, packaging and the questions to ask
How to find where value sits in a first SaaS, package it into plans, and which questions to put to customers, billing platforms and advisors.
-
gtm
Trials, demos and self-serve: how a customer first meets the product
The mechanics of demos, pilots, trials and self-serve, what each asks you to build, and what a U.S. statute says about recurring online charges.
-
gtm
Writing a landing page that says what the product does
A section-by-section plan for a first landing page in plain language, with accessibility basics from W3C and Digital.gov and a check you can run without code.
Pathways
The routes into a company and the routes to capital, side by side.
-
pathways
Choosing a startup program that fits: a decision guide
Batch programs, incubators and community programs differ in length, terms and fit. What research reports, and ten questions to ask before applying.
-
pathways
Using SBA resource partners: SBDC, SCORE, WBC and VBOC
Federal business counseling centers, volunteer advisers, women's centers and veteran centers. What each does, who it serves, and how to find one.
-
pathways
Acquiring a small software product instead of building one: what to check
A checklist of what to verify before buying a small software product: the ownership chain, accounts and data, customer contracts, tax reporting and filings.
-
pathways
Acquisitions, acqui-hires and wind-downs: the exits to recognize
How selling a company, selling its assets, an acqui-hire and a wind-down differ, and the votes, filings and records each can involve, for first-time founders.
-
pathways
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.
-
pathways
From client work to a product: productizing a service business
How a service business can turn repeated client work into a product: what to check about ownership, client data and pricing before the first version ships.
-
pathways
From side project to company: the decision points
When a side project starts to need a legal home, a bank account and written agreements, and the questions each moment raises for solo and student founders.
-
pathways
Joining as a founding team member: what to ask before you commit
Questions to ask before joining an early company: role, equity, pay, work authorization and exit terms, for people changing careers or countries.
-
pathways
Matching a funding route to a stage: a decision guide
A decision guide for early founders: the main routes to capital, what each asks of you, and the questions that connect a route to what you can show today.
-
pathways
Paying a first team before funding: the options and what each risks
Ways early founders pay first helpers without outside funding: fixed fees, wages, deferred pay and shares, what each risks and what to put in writing.
-
pathways
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.
-
pathways
Three ways to start: an idea, a skill, a problem you have lived
Founders begin from an idea, a skill or a problem they have lived. This article sets the three starting points side by side and names what each skips.
Business models
How B2B SaaS, vertical SaaS, marketplaces, platforms and developer products work, and what each asks of a first company.
-
models
API-first products and developer tools
What it means to build a product around its interface, what developers expect from an API, and the early choices on errors, versions and documentation.
-
models
B2B SaaS: how the model works and what it asks of a first company
What business-to-business software as a service is, how it earns money, and the reliability, security, contract and support work it asks of a first company.
-
models
Marketplaces: the two-sided start-up problem
How a two-sided marketplace works, why the first buyers and sellers are hard to win together, and the payments, trust and legal questions the model adds.
-
models
Open-core and open-source businesses
How companies build a business on open-source software, what open core means, what licenses allow, and the questions a technical founder should answer first.
-
models
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.
-
models
Product-led and sales-led growth: choosing between them
What product-led and sales-led growth mean, what each asks of a small team and its product, and a set of questions for choosing a motion without benchmarks.
-
models
Usage-based, seat-based and hybrid pricing models
How seat-based, usage-based and hybrid pricing work, what each one asks of your product and billing, and the questions that help you choose a unit of value.
-
models
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.
Sectors
Considerations for building software in fintech, healthtech, edtech and climate tech. General information, not a claim of experience.
-
sectors
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.
-
sectors
Edtech SaaS: considerations before you build
Questions to settle before you build education software in the United States: student records, children under 13, school official status and web accessibility.
-
sectors
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.
-
sectors
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.
-
sectors
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.
-
sectors
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.
-
sectors
Legal software: considerations before you build
Questions to settle before you build legal software: client confidentiality, supervision, privilege, e-signatures and the unauthorized practice of law.
-
sectors
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.
Operations and wellbeing
Run the company and look after the founder, in general terms and without advice.
-
ops
Coworking and community: what the research shows about staying power
Does working among other founders help a company last? Two published studies, what they measured, and how to use a shared space or a founder community well.
-
ops
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.
-
ops
The longevity paradox: sprint weekly, endure for a decade
Early work runs on weekly sprints, yet public survival data runs on decades. What federal survival curves say about pacing a company for the long haul.
-
ops
A weekly operating rhythm for a founder
How a founder can set a repeating week with a plan, protected work blocks, an admin block and a review, borrowing the idea of fixed-length cycles from Scrum.
-
ops
Books and basic accounting for a software startup
What keeping books means for a small software company, what the IRS says about records, separate accounts and accounting methods, and what to ask an accountant.
-
ops
Burnout: recognizing it and what to change
What a US occupational-health institute says burnout is and is not, the six work-design areas a UK regulator ties to stress, and when to talk to a professional.
-
ops
Choosing and managing a small company's software stack
Criteria for choosing a small company's tools and a light routine to keep them in order, using a US consumer-protection agency's data principles.
-
ops
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.
-
ops
Meetings, async work and decision records for a small team
How a small team can decide which conversations need a meeting, what to write instead, and how to keep a decision record, using the Scrum Guide and GOV.UK.
-
ops
The tax calendar a US software startup should know exists
What the IRS tax calendar lists for a small company, how its due dates are worded, and the questions to bring to a tax professional. General information only.
-
ops
Working through a disagreement with a co-founder
A general process for a co-founder disagreement, what mediation is according to a US agency and a federal court, and whom to ask for help.
Dream
Build
Grow
Fundable
Starting out
Funding and capital
Legal and company basics
Team and hiring
AI-native building
Go-to-market
Pathways
Business models
Sectors
Operations and wellbeing
0 min3 min5 min8 min10 min
Each dot is one article; the amber mark is the desk’s median.
Show the figures as a table
| Group | Articles | Shortest reading time | Median | Longest |
|---|---|---|---|---|
| Dream | 7 | 5 min | 6 min | 6 min |
| Build | 11 | 5 min | 6 min | 6 min |
| Grow | 6 | 5 min | 6 min | 6 min |
| Fundable | 8 | 6 min | 6 min | 7 min |
| Starting out | 14 | 6 min | 6 min | 8 min |
| Funding and capital | 13 | 6 min | 7 min | 8 min |
| Legal and company basics | 8 | 6 min | 6 min | 8 min |
| Team and hiring | 9 | 6 min | 6 min | 7 min |
| AI-native building | 9 | 5 min | 6 min | 8 min |
| Go-to-market | 10 | 6 min | 7 min | 7 min |
| Pathways | 12 | 6 min | 7 min | 7 min |
| Business models | 8 | 6 min | 6 min | 7 min |
| Sectors | 8 | 6 min | 7 min | 7 min |
| Operations and wellbeing | 11 | 6 min | 6 min | 7 min |
Chart: World Enterprise Group Incorporated, counted at build time from the articles on this site at 220 words a minute.
Start a readiness review
Tell WE where the company stands. WE replies to arrange a conversation and a written read of your company's timeline.
A short PDF of the charts and sources, sent by email to the address you give.
Talk to WE : A question that does not fit a form.