Explain the product first
Investors can understand a market from a deck. Customers cannot understand your product from a vision statement. Lead with what it does and for whom, because that also serves the investor better than abstraction.
Two audiences, almost no budget, and a product that will change. The trick is building something that does not have to be thrown away in six months.
A startup website serves early customers and investors at once, which are different readers. The practical goal is something credible now that does not need rebuilding after the next pivot or raise. That usually means a small, well-structured site rather than an ambitious one you cannot afford to maintain.
Investors can understand a market from a deck. Customers cannot understand your product from a vision statement. Lead with what it does and for whom, because that also serves the investor better than abstraction.
Five pages that work outperform fifteen half-finished ones at this stage. It is also cheaper, faster to change, and does not become a maintenance burden you cannot afford.
Your positioning will move. A component-based build where copy and sections can be rearranged without a developer is worth more than a beautiful fixed layout at this stage.
Early-stage credibility comes from people. Named founders with real backgrounds and LinkedIn profiles do more for an early startup than any amount of polish.
Demo, waitlist, trial or contact. Pick one. Startup sites frequently offer four, which fragments an already small volume of interest.
Domain, code, hosting and analytics in the company's name. Sorting this out later, during a raise or an acquisition, is considerably more painful than doing it now.
| Problem | What it costs |
|---|---|
| Vision statement instead of product explanation | Customers leave without understanding it |
| Fifteen pages at pre-seed | Half unfinished, all needing maintenance |
| Fixed layout that cannot be rearranged | Rebuild after the next pivot |
| Founders anonymous | Removes the main early credibility signal |
| Four competing calls to action | Fragments already thin traffic |
| Domain in a founder's personal name | A problem during diligence |
| Ask them | Good answer | Walk away if |
|---|---|---|
| Who owns the site and accounts? | You do, in your own name | Accounts in the agency's name |
| Can I open three live examples? | URLs you can check yourself | Screenshots and a PDF |
| What is explicitly not included? | A written list with change pricing | Everything is included |
| How will we know it worked? | A metric agreed before work starts | Activity reports |
The exclusions question decides whether the final invoice matches the quote.
Less than most founders assume at pre-seed. A small, well-built site that explains the product and can be changed easily is worth more than an ambitious one. Spend the difference on finding out whether people want the product.
Customers, primarily. Investors can read a deck, and a site that explains the product clearly to a customer also demonstrates clarity of thinking to an investor. A homepage hedging between both serves neither.
Component-based, where sections and copy can be rearranged without a developer, and small enough that changing it is cheap. Positioning will move, so optimise for changeability rather than for the current story.
Yes, named, with real backgrounds and profiles. Early-stage credibility comes from people rather than from the company, which has no track record yet. Anonymity costs you more than it protects.
One. Demo, waitlist, trial or contact, chosen deliberately. Startups frequently offer several and fragment traffic that was already thin.
The company, not a founder personally and not an agency. Sorting this out during due diligence is a recurring and entirely avoidable problem.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.