A free startup stack works when every tool has a job, an owner, and a known boundary. Compare six useful free plans, then build a workbook your team can actually maintain.
For a solo founder, begin with a shared decision record and a way to follow up with customers. Add a board when work needs coordination, design software when you have a design problem, and a repository when you are shipping code. These are recommendations by workflow, supported by official plan pages checked October 5, 2026; they are not results of hands-on vendor testing.
Coordinate the work
Trello Free
Use a visual board for tasks moving from planned to finished. Trello lists up to ten collaborators and ten boards per Workspace, with unlimited cards. Free attachments are limited to 10 MB per file and Workspace automation to 250 command runs per month. A board is a useful shared queue; it is not a substitute for a durable decision record. Check partner Power-Up charges separately.
Choose Notion for written decisions, research notes and lightweight operating documents. The Free plan offers unlimited pages and blocks for individuals, but limits blocks for workspaces with two or more members. Uploads are limited to 5 MB per file, page history to seven days, and external guests to ten. AI is a limited trial rather than an unlimited free research service. Confirm whether collaborators need guest access or full membership.
Choose Starter for drafting interfaces and collecting a visual direction. Figma lists unlimited drafts and UI kits on its free Starter plan, alongside limited access to its broader product set. Do not assume every team project, seat type or publishing feature is included simply because an account is free. Check the current plan matrix against the collaboration you actually need before making it your product team's default.
Use Tally for intake, feedback and simple validation forms. Tally lists unlimited forms and submissions within its fair-use guidelines, with conditional logic and calculations included. Custom domains, removing branding and shared-workspace collaboration appear in Pro. A free form can capture answers; it does not establish demand or make the responses representative. Record the collection question and where answers will be reviewed.
Use GitHub when version history, issues and a code repository are the job. Its free plan includes unlimited public and private repositories. Automation and other metered services have allowances and billing conditions; free repositories do not imply unlimited compute, storage or production hosting. Assign ownership of the organization, recovery access and deployment credentials before a contractor becomes the only person able to ship.
Use the free CRM when customer follow-ups are escaping a spreadsheet. HubSpot documents contact, deal and task management, with its free CRM limited to two users and 1,000 contacts and no expiration date. Premium capabilities are separate. A small team can use it to maintain the next action for a prospect; decide who owns data cleanup and export before adding every contact you encounter.
Make the free boundary explicit. Record members, guests, file sizes, usage allowances, branding and export needs. “Free today” and “fits our team” are different decisions.
Give each job one primary home. Two tools holding the same tasks create reconciliation work. Link the decision record from the board rather than duplicating every note.
Define the upgrade trigger before upgrading. Write the concrete event: a third CRM user, a required custom domain, or a file that exceeds the upload limit. Recheck the official plan at that moment.
Build a stack around the next customer
A useful free stack lets you complete an actual customer journey: explain the offer, collect an inquiry, deliver the product, recover from a mistake and follow up. Begin with that journey rather than an inventory of accounts. A software prototype and a consulting business have different needs. A founder selling workshops may need a form, shared documents and a follow-up record long before needing a database, an issue tracker or event analytics.
The six options above are practical operating tools. The broader comparison below adds the infrastructure, research, design and email decisions a software team will encounter. None of these recommendations is a measured vendor ranking or a promise that your company can run indefinitely at zero cost. Official documentation was checked in October 2026; account eligibility, regional billing and the features used by your particular workflow still need verification.
Evaluate the boundary in six passes
Permission: read the commercial-use terms before building. A free personal deployment allowance can exclude a business prototype even before it accepts payment. Revenue is not the only possible test.
Capacity: identify the unit the service actually counts. Contacts, issues, events, recordings, requests, stored bytes and messages are different units. Separate daily allowances from monthly ones.
Completion: perform the entire job with the free account. A design that cannot be exported in your required format or a form whose answers cannot reach the reviewer is an unfinished workflow.
Recovery: restore a meaningful sample. A CSV export does not prove that attachments, permissions, relationships, authentication identities or history will move intact.
Ownership: put the company account, billing access and recovery methods under accountable team ownership. A contractor's personal login is a fragile foundation regardless of price.
Upgrade: obtain the current quote for the actual members, products and usage. Record which problem the purchase resolves and what would still remain outside the subscription.
These passes produce a decision record rather than a universal score. Two vendors can both offer useful free plans while one fits a solo prototype and the other fits a small customer-facing service. A low subscription price can also be the sensible choice when it removes recurring manual work or establishes the recovery guarantees the service needs.
Capacity and migration are separate questions
The first limit you encounter may be a seat, a usage allowance, a collaboration feature, a commercial restriction or an uptime requirement. Ask what happens at that boundary: a rejected request, a stopped deployment, missing analytics, an upgrade notice or a usage bill. Those consequences matter more than a large allowance printed in isolation.
Then ask what leaving requires. Copying plain text is usually simpler than moving a database together with identity records, files and application configuration. An analytics export may preserve raw events while losing the dashboards and cohort definitions used to interpret them. Email infrastructure includes DNS configuration, suppression records, sender reputation and recipient consent. An upgrade in the same vendor avoids some migration work; it does not remove dependence on that vendor.
Do not assume a specific allowance will last until first revenue. A free product can become busy without selling anything, and a quiet product can collect information valuable enough to require stronger recovery before it becomes busy. Forecast from your own workload and test a realistic export before committing the only copy of essential work.
Fourteen options, compared by their actual job
The original broad shortlist includes the fourteen products below. They are alternatives and building blocks, rather than fourteen mandatory subscriptions. Existing Trello, Figma and GitHub comparisons above remain useful; the additional notes here address the larger launch workflow and the decisions their plan pages cannot make for you.
GitHub: source ownership and delivery history
GitHub belongs in a startup stack when the team ships code and needs a shared repository, review history and a recoverable record of changes. Free public and private repositories do not make all associated services unlimited. Inspect Actions, hosted development, storage and any security feature separately on the official pricing page.
Choose one company-owned organization and document who can administer it. Keep deployment secrets out of exported planning notes. Test cloning a repository and restoring the release process from documented steps. A repository copy preserves code; running production also needs configuration, database state and access to the deployment provider. For a team already managing work in repository issues, another tracker needs a clear additional purpose.
Cloudflare: distinguish the website plan from compute
Cloudflare can serve several infrastructure jobs, but its products have separate allowances and billing. The Workers pricing documentation identifies a free plan and a paid minimum of $5 per account per month. That is a Workers price, not a blanket price for Cloudflare's website Pro plan. The Workers limits list 100,000 requests per day and a 10 ms CPU allowance on Free.
Evaluate those limits against the code you actually run. A simple endpoint and a computationally heavy operation consume resources differently. Record which DNS, storage and compute products your application uses instead of describing the whole account as one free service. Keep an export of DNS records and deployment configuration; changing a provider should not depend on remembering dashboard choices.
Supabase: a database needs a recovery plan
Supabase combines managed Postgres with related backend services. Its Free plan currently lists two active projects, a 500 MB database allowance, 50,000 monthly active users and separate storage and egress limits. Automatic backups are not included on that tier, and low-activity free projects can pause. Pro starts at $25 per month, with additional project and usage considerations.
For an experiment, this can be a practical starting point. For customer information, document the backup procedure and test restoration before relying on the database. The official backup guide recommends regular off-site exports for free projects. A database dump alone does not demonstrate that authentication, uploaded files, environment variables and integrations will recover. Estimate those dependencies before calling a migration easy because the database engine is open.
Vercel: commercial permission comes before the invoice
Vercel's deployment workflow can be convenient for personal demonstrations and application previews. Its fair-use guidelines restrict Hobby to non-commercial personal use and define commercial activity more broadly than accepting a first payment. A deployment used for financial gain, including work involving paid employees or consultants, can be commercial.
For a startup project, resolve the plan requirement at the beginning. Do not describe Hobby as a guaranteed free runway until launch or revenue. Compare the actual eligible deployment plan, usage and seat needs with alternatives, and retain a reproducible build that can run elsewhere. Branch previews are helpful for review; they do not establish production suitability or eliminate runtime usage charges.
Linear: an issue limit measures work records
Linear's current Free plan lists unlimited members, two teams and 250 issues. Basic is displayed at $10 per user per month when billed yearly. This is a useful starting point for a team that wants issues, cycles and a shared product queue, but an issue allowance is not a prediction of how many months it will last.
Count the records your workflow creates, including customer requests, operational tasks and bugs. Keep discussion and decisions linked to the relevant issue without making a tracker the only home for research. Before adopting it across departments, test the non-engineering work and export requirements. Select Linear or another primary task system deliberately; maintaining the same queue in Trello and Linear adds reconciliation work.
Figma and FigJam: design and discussion need distinct homes
Use Figma when interface design, prototypes and visual review are the job. FigJam can support workshops and diagrams. The plan matrix matters because drafts, team files, viewers, editors and product-specific seat access are different categories. Check the exact collaboration pattern rather than assuming that everyone invited to a free account gets every capability.
For a first product, keep the active design understandable and archive decisions in a format the team can read without the editor. Test a stakeholder review and a contractor handoff. A visual workshop surface can make reasoning visible, but it only preserves reasoning when someone records the decision, supporting evidence and rejected alternatives. Avoid treating a board full of sticky notes as an automatically usable company memory.
Obsidian: free commercial use, with responsibility for files
Obsidian's license overview states that it is free for personal, commercial and nonprofit use. Commercial licenses are optional support purchases. An older comparison that requires every business user to buy a commercial license is outdated.
Local Markdown is useful for durable notes and portable decision records. The portability of text does not remove the need to back up the device or understand plugin behavior. Optional Sync and Publish are separate services. For a team, agree how records are shared and who owns the authoritative copy; local-first notes do not automatically provide shared permissions, review or synchronization. Test links and attachments when moving a sample vault, not only the words in one file.
Claude: evaluate an actual founder task
Claude offers a free consumer plan. Its current pricing page includes chat, web search, file creation and other features, with plan-dependent usage. Pro is shown at $20 monthly or $200 billed annually. Free chat access is separate from API usage and is not an unlimited production inference budget.
Try it on a specific task: reorganize anonymized interview observations, draft alternatives for a customer email, or challenge the assumptions in a positioning document. Check the result against the underlying evidence. Keep a reusable brief and the approved output outside a chat history. A limitation or model change should not erase the company's reasoning. Avoid unqualified claims that one model is always the best at strategy or long documents without a relevant evaluation.
ChatGPT: broad assistance still needs an owner
ChatGPT's Free Tier FAQ describes free access with separate limits for advanced activities. A free consumer account should not be budgeted as an API service or as guaranteed uninterrupted access to every feature.
Use it where a human can judge the work: outlining a guide, identifying questions to investigate or preparing a first pass at a spreadsheet explanation. Keep the source data, instructions and reviewed final answer together. Check customer-information handling and organizational requirements before uploading material. For a founder choosing between assistants, run the same representative task and compare accuracy, effort to correct, usefulness and available access rather than collecting several subscriptions by default.
PostHog: product allowances are separate
PostHog's pricing page separates product analytics, replay, flags and other products. Current free monthly allowances include one million analytics events, 5,000 recordings and one million feature-flag requests. Those are separate units; replay is not included inside one shared event allowance.
Define a small event plan around decisions such as whether visitors complete onboarding. Verify captured events and exclude sensitive information deliberately. Billing caps can constrain spending while also dropping further data or changing flag responses once limits are reached. Decide which consequence is acceptable. Analytics supports investigation; an event count alone does not explain customer motives or establish product-market fit.
Trello: make the board the shared queue
The Trello comparison above gives the current board, collaborator, attachment and automation boundaries. A board fits early teams when moving work through a few states is more useful than a complex tracking hierarchy. Name those states in the team's own workflow and define what counts as finished.
Write a next action, accountable owner and evidence link on each meaningful card. Keep research and decisions accessible from the card instead of pasting multiple competing copies. Before using the board for external collaborators, test their actual access. A free board is a coordination tool; it does not automatically enforce approvals or recover all information from an export.
Canva: publishing rights and premium assets matter
Canva is useful for social graphics, simple presentations and lightweight marketing production. Its pricing page distinguishes Free from paid plans and trials. Check the selected template, asset and output requirements rather than assuming every item visible in the editor is free.
The licensing explanation also matters for commercial work. Keep track of the material actually used and its permitted use. Establish a small reusable visual system so the founder can update a graphic without redesigning everything. If editable handoff or a particular brand feature is necessary, test it before promising a client that the free plan completes the job.
Resend: daily email volume can be the first limit
Resend's transactional pricing currently lists 3,000 emails per month and 100 per day on Free. A one-day announcement can exceed the daily allowance even when the monthly total is small. Pro is shown at $20 per month for 50,000 emails, with additional-email pricing and other conditions.
Separate password resets, purchase receipts and other transactional messages from a marketing-campaign decision. Configure the sending domain, monitor bounces and preserve suppression information. Test failure and retry behavior; sending twice is not a harmless substitute for a delivery check. A free allowance reduces the initial service bill, but domain ownership and reliable customer communication remain operational responsibilities.
Perplexity: use citations as leads to inspect
Perplexity's plan guide describes a Standard free plan with basic searches, limited advanced searches and limited uploads. Advanced-model access and paid product features differ by plan.
It can help a founder discover sources for a market question. Open those sources, check dates and record what the evidence actually supports. A generated answer with links is not a completed competitive audit. Keep factual notes separately from interpretation, particularly when comparing prices or commercial terms. Its consumer subscription and API platform are different purchasing decisions.
Your stack, with an owner.
This local workbook records your decisions. It does not sign up for services, check accounts, calculate future bills or automatically certify free-tier fit. Status is your manual assessment. Nothing is saved automatically; export before leaving.
CSV requires exactly these column names: job, tool, owner, status, source, checked, limit, trigger, exit. Status must be Needs check, Fits, or Upgrade needed. Date is optional YYYY-MM-DD. An invalid import leaves the existing workbook intact. CSV imports use PapaParse; JSON remains available if that library cannot load.
Assemble only the jobs you need
Start with a written offer, a way to collect inquiries and a record of follow-up. If you are shipping software, add source control and an eligible deployment arrangement. Add a database when the product needs persisted information, rather than because a checklist contains one. Add analytics when you have a defined decision and can verify the event implementation.
A solo service founder
A consultant validating an offer can begin with shared documents or local notes, a form such as Tally and a follow-up spreadsheet. Canva may handle a simple presentation. Trello becomes useful when multiple deliverables need a visible queue; a CRM becomes useful when contacts and next actions outgrow the spreadsheet. None of those steps requires a code repository or a product database merely to look like a startup.
The practical test is whether an inquiry reaches an owner, the owner can deliver the promised work and the customer gets a reliable response. Record where consent and agreements live. Check export and backup before the spreadsheet becomes the only record of the business.
A two-person software team
GitHub can hold code and reviews. Choose a deployment plan that permits the intended commercial activity; Vercel Hobby should not be assumed eligible. Cloudflare products may cover particular edge or hosting needs, with each product assessed separately. Supabase can provide backend components when its limits and recovery arrangement fit the experiment.
Pick one primary tracker: repository issues, Linear or Trello. Add Figma when interface design needs a shared working surface. Use a decision record linked from those tools. Add Resend only when the product needs transactional email, and PostHog only with a tested event plan. The useful stack is the smallest set that completes delivery and recovery, even if that set includes a paid plan.
A small team preparing for launch
Growth changes the requirements before it changes every allowance. Inviting a contractor may require a different permission model. Keeping customer information may require backup and access review. Publishing a commercial product can change hosting eligibility immediately. A launch campaign can create a daily email spike that a monthly estimate misses.
Conduct a launch review with the actual owners present. Check access from a fresh account, recover a sample record, simulate a failed notification and verify where usage is monitored. Document the expected response to each limit. An alert is useful only when someone knows what to do with it.
A worked example: a neighborhood repair service
This fictional example shows the decisions, not a benchmark or a measured success story. Two founders are testing a booking service for neighborhood repair businesses. Their first milestone is a reviewed list of ten potential business partners and a demonstrable booking flow. Their offer can be tested through interviews and a manual scheduling pilot before implementing a complete marketplace.
The product owner keeps interview evidence and positioning decisions in a shared document. A form collects requests; a spreadsheet records the next follow-up. A single Trello board tracks preparation, calls and pilot delivery. The technical founder stores a prototype in GitHub and selects deployment only after checking whether the intended business demonstration meets commercial-use terms. A database is introduced when the pilot needs persistent booking records, with an off-site backup and restore test.
Their workbook records each tool as Needs check until that owner completes the relevant review. They do not label a stack as free merely because the vendor homepage says so. They also leave AI assistants outside the core delivery path: a model can help draft interview questions, but reviewed questions and interview notes remain available if the assistant hits a limit.
A complete decision record
Job: collect a repair business's interest in a pilot.
Tool: a form service evaluated for the actual intake workflow.
Owner: the founder responsible for partner research.
Status: Needs check until collection, export and access tests are complete.
Source: the current official plan and relevant privacy documentation.
Checked: the date the owner performed those checks, rather than the date someone copied a vendor claim.
Limit: the specific collaboration, branding or response boundary relevant to this form.
Trigger: move to a different arrangement if the agreed workflow requires a capability not included in the free account.
Exit: export a sample response, confirm its fields and attachments, and store the reviewed file in the project's agreed location.
The same structure works for every row, while the detail changes by job. The database exit must cover data and dependent services. The email exit must include domain configuration and suppression records. The design exit must preserve the assets and format required by the next editor.
Run the review as a practical workflow
List the next milestone and the actual jobs required to reach it.
Remove duplicate homes for tasks, notes and contacts before choosing additional products.
Add candidate rows to the workbook, with an accountable owner and official source.
Have each owner test the complete job, including a meaningful export or recovery exercise.
Write the first relevant boundary and the response if it is reached.
Obtain a quote where commercial eligibility, reliability or collaboration already requires payment.
Export JSON to preserve the exact workbook, and Markdown for a readable review.
Revisit the record when the team, workload, plan terms or information sensitivity changes.
This workbook intentionally leaves suitability under human review. It does not inspect vendor accounts, fetch plan changes, certify privacy compliance or forecast a bill. Its genuine utility is collecting the decisions, preserving multiline notes and making them portable. Import a custom CSV with the stated headers, then restore a JSON export to verify that the name and records survive.
Understand what the first paid month buys
Budget from a current quote rather than multiplying fourteen headline prices. Separate per-member charges, shared account subscriptions, metered services, domain and email costs, taxes and optional products. An annual rate is not the same cash commitment as a month-to-month plan.
For example, Linear currently displays Basic at $10 per user per month billed yearly: three billed users imply a $30 monthly equivalent and a $360 annual base commitment before taxes or other terms. Supabase Pro starts at $25 per month, but multiple projects and usage can change the bill. Resend Pro is displayed at $20 per month with its included transactional allowance. These are separate examples, not a recommended bundle or a guaranteed combined quote. Workers' $5 minimum belongs to that compute product, not Cloudflare website Pro.
Prioritize spending that resolves an actual constraint. Company domain ownership and suitable email may be useful early; recovery or eligible commercial hosting can be essential. A paid assistant may save review time for some founders, but it cannot replace a source record or purchase demand. A reasoning workspace can be worth buying when its specific shared workflow fits; ordinary documents or an Obsidian canvas can also preserve decisions if the team maintains them.
Seats, usage and the cost of switching
A solo founder may be the only billed editor while collaborators are viewers or guests, but that arrangement must be supported by the vendor's current terms. A three-person team should identify which people actually need paid capability. A five-person team may care more about administration, access removal and recoverability than about a small seat-price difference.
Also estimate the human work of switching: preparing exports, rebuilding integrations, reviewing access, testing migrated records and training the team. Those costs do not fit neatly into a subscription table. A cheaper service can cost more when it duplicates an existing workflow or requires repeated manual repair.
Credits, trials and alternatives
A recurring allowance, a countdown trial and promotional credits are different arrangements. A trial is useful for evaluating a purchase; it should have an explicit end decision. Credits can offset eligible charges temporarily, but they do not remove the underlying price or guarantee approval.
The AWS Activate program publishes current startup eligibility and credit conditions. Other cloud and startup programs have their own application and expiration terms. Apply through the relevant official program, check what services the grant covers and record the date it expires. Do not build an architecture solely to spend credits. Estimate the ordinary bill before accepting a temporary discount and decide who monitors remaining credit and usage.
Broaden the shortlist when a requirement calls for it
Railway and Render are hosting candidates to investigate when the application needs a different deployment model. Neon and Turso are database candidates when a separate database is preferable to an integrated backend. Sentry is relevant to error tracking; Plausible and Umami are relevant to a simpler analytics approach. Self-hosting an open-source tool still uses infrastructure and operator time.
Excalidraw can be a diagramming candidate. Consumer document and spreadsheet products may handle an early shared record, while business-domain email is a separate decision. Zapier and Make are candidates for a first integration when their actual operation limits fit. Brevo and MailerLite belong in a marketing-email comparison rather than being assumed interchangeable with transactional delivery.
These are discovery leads, not verified claims that every listed product offers an indefinitely free commercial plan. Check current official terms for the chosen job before adding it to the workbook. A longer shortlist helps only when it resolves a specific unmet requirement.
Mistakes that make a free stack expensive
Buying accounts before defining jobs: each added home increases access and reconciliation work. Map the customer journey first.
Waiting for revenue to check permission: commercial definitions can apply before a payment arrives. Check the actual intended activity.
Treating every limit as a monthly counter: daily email limits and compute time can matter long before a large monthly allowance.
Confusing portable data with complete recovery: a database export or folder of Markdown still needs tested attachments, configuration and dependent services.
Duplicating tasks across tools: two authoritative queues require someone to maintain agreement. Link records instead.
Keeping ownership in a personal account: recovery and access removal become difficult when the only administrator leaves.
Assuming free AI is an API budget: consumer access, paid subscription and developer usage are different products.
Using a paid plan as a substitute for evidence: a CRM cannot make a prospect qualified; analytics cannot explain intent on its own; a model cannot establish that its market estimate is correct.
Rejecting a useful paid tool solely to preserve a zero-dollar claim: the right question is whether the purchase solves a real delivery, safety, recovery or time problem.
Questions founders ask before adopting a stack
Can a startup begin with free tools?
Yes, when the required jobs fit the actual eligibility and limits. Domain ownership, suitable commercial hosting, backup, transaction charges and business email may still require a budget. Describe what is covered rather than promising an entirely free company.
Which tools are necessary on day one?
An accessible offer, a way to learn from prospective customers and a durable next-action record. Add product infrastructure when delivery requires it. A repository is necessary for some software teams and irrelevant to many early service experiments.
Should I adopt all fourteen options?
No. The options cover different jobs and include overlapping task and AI tools. Choose one primary home per recurring job and leave the rest as alternatives.
Is Obsidian free for business use?
The current license overview says yes; a commercial license is optional. Sync, publishing and the work of managing shared files are separate considerations.
Can I use Vercel Hobby for a startup prototype until my first payment?
Do not assume that. The guidelines restrict Hobby to non-commercial personal use and define commercial activity beyond receiving payment. Check the proposed deployment against the official rules at the start.
Which free project tracker should I choose?
Trello can fit a visible workflow board, Linear can fit a software issue process, and repository issues can reduce duplication for a team already working in GitHub. Test your own task cycle and the current limits before choosing.
Is a free database safe for customer records?
Safety depends on access, backups, recovery and the information involved. Supabase Free does not include automatic backups; plan and test the documented off-site export procedure. A database engine choice alone is not a recovery plan.
Does PostHog offer one million free recordings?
No. The current pricing separates one million analytics events from 5,000 session recordings and other product allowances. Count the product and unit you actually use.
Can I send 3,000 Resend emails in a single day on Free?
The displayed free allowance has a 100-email daily limit as well as a 3,000-email monthly limit. Check both against the sending pattern and test delivery behavior.
Which free assistant is best?
Evaluate your own representative tasks, evidence accuracy, correction effort and available access. Avoid treating a broad recommendation as a benchmark for every model, document or founder.
Are citations in an AI answer sufficient research?
No. Open the original material, check dates and verify that each source supports the statement. Retain the evidence and reviewed conclusion separately from the generated answer.
Are startup credits better than a recurring free allowance?
They serve different purposes. Credits offset eligible costs temporarily and may require approval; a recurring allowance resets under the service's plan. Compare the ordinary cost and recovery requirements after credits end.
Is an upgrade cheaper than migrating?
Sometimes. Compare the complete quote with the time and risk of a tested migration. Staying avoids some transfer work while retaining the vendor dependency.
Do these recommendations prove vendors have been hands-on tested?
No. The comparison uses current official documentation and workflow reasoning. The local workbook's import, export and restore behavior is a separate interactive feature; it does not test external vendor accounts.
Does the workbook calculate future subscription costs?
No. It stores your manually assessed limits, owners, triggers and exit plans. Obtain an account-specific quote and use the workbook to record the decision.
How should I preserve my workbook?
Download JSON for exact restoration of the name and records. CSV supports interchange, including quoted multiline fields, and Markdown supports readable review. The page has no automatic cloud save.
When should I review it again?
When the team, workload, plan terms or recovery needs change, and before relying on a new commercial launch or customer-data workflow. Assign the review to the relevant owner rather than leaving it as an unowned reminder.
Keep the work. Keep an exit.
Review this record when your team or usage changes. Try a real export from each selected vendor before making it the only home for important work. This workbook's exports are your planning notes, not exports from those services.
Is a free startup stack enough?
It can be enough for an early workflow that fits the current limits. The deciding factors are your collaboration, usage and recovery needs, not a universal number of apps. Infrastructure, domain names, transaction charges and optional add-ons may sit outside a product's free plan.
Should I choose all six tools?
No. Choose the jobs you need now and remove duplication. A nontechnical founder may not need a code repository; a solo founder may not need a CRM until follow-up becomes hard to track.
What happens to my inputs?
The workbook stays in this page's memory. Export CSV, JSON or Markdown to keep it. JSON restores the workbook name and records; CSV restores the records. No account or cloud sync is provided by this tool.