Founder help
AutoBuilder Support
Find answers, recover from issues, and keep building. Most problems can be solved through guided support before you create a ticket.
Search
Search support
What is AutoBuilder?
GeneralAutoBuilder is a startup execution layer for hackathon and indie founders.
- Open /analyze or /startup-idea-analyzer
- Add target user, pain, and market
- Review the report and save to workspace
I cannot sign in
AccountMay need supportSign-in issues are usually email typos, password, or browser session problems.
- Verify email spelling
- Use /forgot-password
- Try incognito/private window
I forgot my password
AccountMay need supportUse forgot-password and check spam before contacting support.
- Open /forgot-password
- Enter account email
- Check spam and promotions
Analyzer did not generate a report
AnalyzerMay need supportUsually input too short, network, or browser issues.
- Add target user and painful problem
- Refresh the page
- Retry with shorter input if very long
Report feels too generic
AnalyzerVague inputs produce vague reports.
- Name one target user
- Describe the painful moment
- Add market and stage
Score seems too low
AnalyzerScores are planning estimates, not investment advice.
- Read the weakness section first
- Use the stronger version
- Follow first-release plan
Workspace is not saving
WorkspaceMay need supportWorkspace saves to this browser until cloud sync ships.
- Open /workspace
- Run analyzer again and save venture
- Avoid private mode if you need persistence
Privacy and sharing reports
PrivacyMay need supportPrivate by default. Sharing is opt-in.
- Check visibility on saved venture
- Use private mode for drafts
- Regenerate share link if needed
Billing and refunds
BillingMay need supportBilling questions are reviewed case by case.
- Read /docs/pricing-billing
- Read /refund-policy
- Contact support with account email and receipt
Launch checklist
LaunchUse launch checklist from report and /launch-sprint.
- Complete first-release plan
- Open /launch-sprint or dashboard launch checklist
- Ship one proof milestone
AI workforce tasks
ProductPlanning agents — not legal or financial professionals.
- Read /docs/ai-workforce
- Pick one task to execute this week
- Use execution brief in your editor
Build and report recovery
RecoveryMay need supportRecover weak outputs with stronger context or support.
- Identify recovery type: report, workspace, account, or deploy
- Apply first fix from docs/build-recovery
- Copy inputs before retry
Fast paths
Fast help paths
Account
I cannot sign in
Account
I forgot my password
Analyzer
My analyzer report did not generate
Analyzer
My report feels too generic
Workspace
My workspace is not saving
Billing
I have a billing question
Billing
I want a refund review
Recovery
I need launch/build recovery
Quality
I want to improve my idea
Support
I want to contact support
Self-service diagnostics
Answer two questions for likely fixes and related docs.
What are you trying to do?
What happened?
Recommended
Analyzer did not generate a report
Add clearer idea, target user, pain, and market. Refresh and retry. Copy your text before refreshing. Shorten extremely long inputs.
Startup analyzer docs →Page is blank or broken
Refresh, clear cache, try another browser, check connection. Contact support with URL, browser, and screenshot.
System status →I cannot sign in
Check email spelling, reset your password, try a private window, and clear cache. If auth is in preview on this build, use workspace on this device until cloud accounts ship.
Forgot password →Workspace is not saving
Sign in when available, refresh, copy report text before leaving, and check /workspace and /dashboard. Do not clear browser data if you need local saves.
Founder workspace docs →This issue may need support if fixes do not work.
Recovery
Failed builds and recovery IDs
Calm support paths — your work is saved.
- Find your recovery ID in Proof Lab or workspace proof panel.
- Open the support summary — what happened, what is saved, what did not publish.
- Copy the Cursor recovery packet and fix locally with pnpm build.
- Retry smaller scope; use rollback or quarantine if failures repeat.
- Credit recovery may apply — human review; not automatic refunds.
- Public proof and sharing always require separate approval.
Triage
Choose your support path
Pick the category that matches your situation.
Build Recovery
When to use
Generation failed, output is broken, or you are stuck after an error.
Include
Error text, intake summary, what you expected, plan level.
Deployment Help
When to use
Hosting, env vars, or go-live blockers.
Include
Host name, deployment URL, logs (no secrets).
Account and Billing
When to use
Plan changes, invoices, access issues, refund questions.
Include
Account email, plan name, charge date if relevant.
Product Feedback
When to use
Feature ideas, quality issues, or workflow suggestions.
Include
Use case, severity, whether it blocks launch.
Scope
What we can help with
Early-stage execution support, not legal or investment advice.
- ✓Failed builds and broken pages
- ✓Confusing or generic generated output
- ✓GitHub setup questions
- ✓Deployment blockers
- ✓Missing environment variables (guidance only, never share secrets)
- ✓UI and layout issues
- ✓Project direction and launch checklist
- ✓Billing and plan questions
- ✓Refund review (case by case)
- ✓Feature requests
Checklist
What to include in a support request
Better tickets get faster, more useful replies.
- 1.Your account email
- 2.Project or venture name
- 3.Project URL if deployed
- 4.What you were trying to do
- 5.What happened instead
- 6.Screenshot if possible
- 7.Build or deployment error text
- 8.Whether this blocks launch
- 9.Your plan level
Priority
Severity levels
We use target priorities, not published response-time guarantees.
Autobuilder or analyzer appears unavailable for many users.
Highest target priority
Paying customer cannot build, deploy, or complete core workflow.
High target priority
Broken output or workflow issue with a workaround.
Standard queue
UI polish, docs question, non-blocking confusion.
When capacity allows
Ideas and non-urgent improvements.
Logged for product review
Philosophy
Support Philosophy
How we think about help when something goes wrong.
A failed build should become a clearer next step, not a dead end. When AutoBuilder gets something wrong, our goal is to understand what happened, help recover the project when possible, and improve the system so future builders hit fewer blockers.
Build recovery
Turn failures into forward motion
The goal is not only to close a ticket. It is to recover your project and reduce repeat failures.
Diagnose the error
Capture message, step, and intake used.
Identify likely cause
Scope, context, env, or plan limits.
Suggest the fix
Concrete next edit or retry path.
Retry or rebuild
Smaller slice, clearer constraints.
Log the pattern
Anonymized patterns improve Autobuilder.
Improve future builds
Product learns from repeated failure modes.
Report an issue
Submit opens your email client with a prefilled message to support@autobuilder.noaerth.com. Full in-app intake is coming soon.
Community
Feedback and community
Help shape Autobuilder. Discord and public community are coming soon.
Show your build
Coming soonShare what you shipped with Autobuilder (coming soon).
Suggest a template
Coming soonIndustry-specific intake templates (roadmap).
Billing
Refunds and billing
Reviewed case by case based on access, usage, technical issues, and plan terms.
If you believe Autobuilder did not function as expected, contact support with your account email, plan, issue summary, and what blocked you. Refunds are reviewed based on product access, usage, technical issues, and plan terms. We do not promise automatic refunds.
Read full Refund Policy →Read Builder Momentum Guarantee →Stuck does not mean done.
Autobuilder is designed to help founders move through messy early-stage execution. If a build fails, a deployment breaks, or the output is not strong enough yet, support should help turn that friction into a clearer next step.