Best Practices: Build Faster with HeyBoss
Learn proven strategies and tips to build websites faster, avoid common mistakes, and get the most out of HeyBoss's AI-powered platform.
Key takeaway: Following these best practices can cut your development time by 50-70% while producing higher-quality results.
1. Start with Clear Requirements
Be Specific in Your Prompts
The more specific you are, the better results you'll get:
Bad: \"Build me a website\"
Good: \"Build a landing page for my AI SaaS product with pricing table, testimonials, and email signup. Style should be modern and clean with blue/white colors.\"
Bad: \"Add a contact form\"
Good: \"Add a contact form with fields for name, email, phone, and message. Include form validation and send submissions to [email protected]\"
Provide Examples and References
Show, don't just tell:
Include URLs of websites you like: \"Make it look like stripe.com\"
Provide screenshots or mockups if you have them
Share competitor websites: \"Similar to [competitor.com] but with X feature\"
Break Down Complex Projects
Don't try to build everything at once:
Start with core features (MVP)
Test and refine
Add advanced features iteratively
Polish and optimize
2. Choose the Right Mode
When to Use Chat Mode
Content updates - Changing text, images, colors
Small additions - Adding sections, components, features
Quick iterations - Fast, low-cost changes
Clarifying requirements - Discussing what you want
Cost: Lower credit usage, faster responses
When to Use Code Mode
Complex functionality - Advanced features, custom logic
Structural changes - Major redesigns, architecture changes
Debugging - Fixing errors, performance issues
Custom integrations - APIs, databases, third-party services
Cost: Higher credit usage, more thorough implementation
When to Use Quick Edit
Typo fixes - Correcting spelling, grammar
Image swaps - Replacing photos, logos
Link updates - Changing button URLs, navigation
Minor color changes - Adjusting text or button colors
Cost: FREE! No credits used
Pro tip: Always try Quick Edit first for simple changes. Save credits for AI-powered features!
3. Prompt Engineering Best Practices
Structure Your Prompts
Use this proven template:
What: Describe what you want built
Why: Explain the purpose/goal
How: Specify any technical requirements
Style: Describe design preferences
Example: \"Create a pricing table (WHAT) to convert free users to paid plans (WHY) with 3 tiers showing monthly/annual pricing and Stripe checkout integration (HOW). Use modern, clean design similar to Linear.app (STYLE).\"
Be Conversational but Clear
Use natural language - AI understands context
Ask follow-up questions to refine
Provide feedback: \"That's close, but make the header bigger\"
Don't overthink - AI is smart!
Use Constraints to Get Better Results
Constraints improve quality:
Design constraints: \"Use only blue and white colors\"
Content constraints: \"Keep all text under 50 words\"
Technical constraints: \"Must work on mobile\"
Business constraints: \"Show pricing in USD and EUR\"
4. Leverage Built-in Features
Use Templates and Cloning
Don't start from scratch:
Templates: Browse HeyBoss templates for quick starts
Clone websites: Copy designs you like and customize
Redesign: Modernize your existing site automatically
Remix: Adapt existing projects for new purposes
Integrate Smart Tools
Use HeyBoss's powerful integrations:
Email automation: Set up Loops.so flows automatically
Analytics: Add Google Analytics with one command
Payments: Integrate Stripe checkout in seconds
Database: Use built-in MongoDB for data storage
Authentication: Add user login without code
Utilize the App Store
Browse and install pre-built plugins:
Calendars, forms, chatbots
Payment processors, CRMs
Analytics, SEO tools
Social media integrations
5. Organize Your Projects
Use Descriptive Names
Bad: \"My Website\", \"Project 1\", \"Test\"
Good: \"SaaS Landing Page v2\", \"E-commerce Store - Fashion\", \"Client Demo - Restaurant\"
Save Versions Before Major Changes
Before big edits:
Note current version number (shown in history)
Make your changes
If something breaks, revert to previous version
Keep Related Projects Together
Organize by:
Client name (\"Acme Corp - Homepage\", \"Acme Corp - Blog\")
Project type (\"Portfolio Sites\", \"Client Work\", \"Personal Projects\")
Status (\"Active\", \"Archive\", \"Templates\")
6. Testing and Quality Assurance
Always Preview Before Publishing
Click "Preview" to see your site live
Test all links and buttons
Fill out forms to ensure they work
Check mobile responsiveness
Test on different browsers
Mobile-First Mindset
Over 60% of traffic is mobile:
Always check mobile preview
Test touch interactions
Ensure text is readable without zooming
Verify images load properly
Check navigation on small screens
Performance Optimization
Optimize images: Compress before uploading
Minimize features: Only include what you need
Test load speed: Use preview to check performance
Avoid heavy animations: On mobile especially
7. Common Mistakes to Avoid
❌ Being Too Vague
\"Make it look better\" is not helpful. Instead: \"Increase font size to 18px, change background to white, add more spacing between sections.\"
❌ Trying to Do Everything at Once
Build incrementally. Don't ask for 20 features in one prompt. Add 2-3 features at a time and test.
❌ Not Providing Content
AI can generate placeholder content, but you'll get much better results providing actual text, images, and data upfront.
❌ Ignoring Errors
If something doesn't work, don't ignore it! Ask the AI to fix it immediately or use Code Mode for complex debugging.
❌ Skipping Quick Edit
Don't waste credits on simple changes. Use free Quick Edit for typos, image swaps, and minor tweaks.
❌ Not Using Version Control
Before major changes, note the current version. If something breaks, you can revert instantly.
❌ Copying Entire Websites
When cloning, customize enough to make it unique. Don't create exact copies - differentiate your brand!
8. Advanced Pro Tips
Batch Your Changes
Instead of:
Prompt 1: \"Change header color\"
Prompt 2: \"Update footer text\"
Prompt 3: \"Add logo\"
Do this:
Single prompt: \"Change header color to blue, update footer text to '© 2025 Company', and add logo in top-left corner\"
Result: Faster, cheaper, more consistent
Use Reference Projects
Create a \"template\" project with your brand colors, fonts, common sections. Clone it as a starting point for new projects.
Leverage Knowledge from Documentation
Tell the AI to follow specific patterns:
\"Create a pricing page like Stripe's documentation\"
\"Follow Material Design guidelines\"
\"Use the same structure as my previous project\"
Iterate with Feedback Loops
Build initial version quickly
Get user feedback (show to friends, colleagues)
Make targeted improvements
Repeat until perfect
9. Credit Management
Maximize Free Features
Use Quick Edit for all simple changes (FREE)
Clone templates instead of building from scratch
Prepare content before starting to avoid back-and-forth
Be specific in prompts to avoid multiple iterations
When to Use Credits Wisely
High-value credit usage:
Complex new features
Major design changes
Custom integrations
Database setup
Advanced functionality
Low-value credit usage (avoid):
Fixing typos (use Quick Edit)
Swapping images (use Quick Edit)
Minor color changes (use Quick Edit)
Vague requests that need re-work
Auto-Recharge
Enable auto-recharge to never run out mid-project. You can set:
Minimum credit threshold (e.g., auto-buy when below 100 credits)
Purchase amount (e.g., buy 500 credits each time)
Monthly budget cap for safety
10. Getting Help
Use In-App Help
Click the "?" icon for contextual help
Check tooltips on buttons and features
Read in-app guidance and suggestions
Search Documentation
Before asking support:
Search Help Center at help.heyboss.ai
Browse articles by category
Check FAQ sections
Review example projects
Contact Support Effectively
When contacting support, include:
Project name or URL
What you're trying to do
What's happening instead
Screenshots if relevant
Exact error messages
Response time: Most support requests answered within 24 hours. Urgent issues prioritized.
Common Questions
How do I build faster without sacrificing quality?
Use templates and cloning as starting points, be specific in prompts, use Quick Edit for minor changes, and iterate in small batches. Test frequently and get user feedback early.
What's the biggest mistake beginners make?
Trying to build everything at once with vague instructions. Instead: Start with MVP, be specific, iterate gradually, and test each change.
Should I use Chat Mode or Code Mode?
Use Chat Mode for 80% of tasks (faster, cheaper). Switch to Code Mode only for complex functionality, debugging, or major architectural changes.
How can I reduce credit usage?
1) Use Quick Edit for simple changes (FREE), 2) Be specific to avoid re-work, 3) Batch multiple changes in one prompt, 4) Use templates/cloning, 5) Prepare content upfront.
What if I'm not getting good results?
1) Be more specific in prompts, 2) Provide examples or references, 3) Break requests into smaller tasks, 4) Try different phrasing, 5) Ask the AI to explain what it's doing.
How do I organize multiple projects?
Use descriptive names (\"Client - Project Type\"), save versions before big changes, group related projects, and create template projects for common patterns.
Key Takeaways
Remember these core principles:
Be specific - Clear prompts = better results
Start simple - Build MVP, iterate gradually
Use the right tool - Quick Edit (free) → Chat Mode → Code Mode
Provide examples - Show reference URLs, explain goals
Test frequently - Preview after each change
Leverage features - Templates, cloning, integrations
Manage credits - Use free features, batch changes
Iterate and refine - Perfect through small improvements
Next Steps
Now that you know the best practices, try them out:
Start a new project with a specific, detailed prompt
Use Quick Edit for your next simple change
Clone a website design you admire
Batch 3 changes into one prompt
Test your project on mobile
Happy building! 🚀
See also: Website Cloner | Quick Edits | Three Editing Modes
Need help? Contact Support for assistance.