Full brand site — 8–12 pages, CMS, analytics — live in 3 weeks. The same delivery process that shipped GigEasy from zero to investor demo.
- Design
- Build
- Launch
fixed-price project
Who this is for
You just closed a round or you're one week out from closing it. You have a logo, maybe a pitch deck, and a hard deadline — investors, candidates, or press will start asking for a real URL soon. You don't have six weeks to vet an agency, and you know a Squarespace template is going to read exactly like what it is.
The pain today
- Investors and candidates Googling you and finding nothing — or a Linktree
- No time to run a five-vendor selection process before the demo
- Off-the-shelf templates that undermine your positioning on first glance
- An information architecture you'll have to scrap the moment you hit Series A
- Copy and design stuck in a loop because neither side has started
The outcome you get
- Investor-grade site live in 3 weeks, built on Next.js and deployed on Vercel
- 8–12 pages with URL structure and component system that holds to Series A
- CMS configured from day one — Sanity, Contentful, or Notion — so marketing self-serves
- Analytics wired at launch: GA4, Plausible, and HubSpot ready on day one
- 1-year bug warranty + Work Made for Hire — you own the code, Figma, and docs
What investor-grade actually means
It does not mean flashy. It means credible. A launch site needs a positioning statement a non-expert can repeat in one sentence, some evidence the team has shipped real things, a simple product or service explanation, a careers page (because you're hiring the moment you close), and a contact path that actually reaches the founder.
Visually, intentional beats impressive. A clean type system, two or three brand colors, one good photo, and motion used with restraint. No AI-generated hero images. No pastel blob abstracts. Investors form an opinion on your clarity and maturity within the first ten seconds — and that opinion travels to the board.
Core Web Vitals matter here too. A site that scores green on Lighthouse is a small but real signal. It says the same discipline that built the product went into the marketing layer. Every site I ship passes Core Web Vitals before DNS flip.
Investor-grade site live in 3 weeks, built on Next.js and deployed on Vercel
The pages you actually need at launch
Most founders over-engineer the launch scope and then delay. Five to seven pages is the right target for a seed-stage site. A homepage, about, product or service page, careers, contact, and a blog scaffold you can populate later. That is it.
The blog scaffold matters even if you have zero posts. It signals content intent to search engines from day one and gives your marketing hire something to build on immediately. Same logic for a case studies or customers section: ship the structure with one placeholder, and filling it becomes a one-day task.
The one page founders always forget is a dedicated careers page. At seed you post two or three roles. At Series A it becomes one of the highest-traffic pages on the site. Building it properly from the start — with an ATS embed or a structured list you can hand off to an ops person — costs almost nothing at launch time and saves a full rebuild six months later.
3 weeks: From kickoff to investor demo.
IA that holds past the seed round
The most expensive mistake I see on startup sites is designing for where the company is today. At seed you have one product. At Series A you have two products, a customer story library, a changelog, and a careers section with 20 active openings.
I build the information architecture with that future in mind. Clean URL conventions: /products/x, /customers/y, /blog/z. A component system that supports adding new sections without a redesign. A CMS schema that treats case studies and blog posts as first-class structured content, not afterthoughts.
The site launches lean, but it does not need a rebuild six months from now when your marketing headcount doubles. That distinction matters when you are paying for rebuilds out of Series A dollars.
My 3-week launch sprint
Week one: kickoff call, 90-minute positioning workshop, wireframes, copy first draft, visual direction sign-off by Friday. You see the visual direction before a single line of code is written.
Week two: full design, content finalization, CMS schema build, development starts. The design and development phases overlap by design — I work across both, so there are no handoffs that cause delays.
Week three: build completes, analytics wiring, QA on real devices, Core Web Vitals pass, staging review, a training session for whoever will manage the CMS, then DNS flip. You get daily async updates throughout and one 30-minute weekly call. Three weeks is tight. It works when there is one senior engineer on every layer — design, frontend, CMS configuration, analytics, deployment — instead of a five-person agency team with two layers of account management in between.
GigEasy was Barclays and Bain Capital-backed fintech with an investor demo scheduled three weeks out. I designed, built, and shipped the investor-facing marketing site and the MVP worker platform in that window. The demo hit. Three weeks vs the typical 10-week cycle for a comparable build — that delta matters most when a funding milestone is on the clock.
Choosing the right CMS
The CMS decision is driven entirely by who will actually edit the site in the next 12 months and how much structure they need.
Sanity is my default for marketing-heavy teams that will publish case studies, blog posts, and landing pages at volume. The structured content model is worth the initial setup investment. Contentful suits larger teams with existing editorial workflows. Notion-as-CMS works well for lean founder-only editing — low friction, minimal training, familiar interface. MDX in the repo is right for engineering-led teams that want content as code.
All four options ship with the same blog and case study content types ready on day one, even if you have no content yet. The structure is there; filling it is a one-day task for a marketing hire or a short follow-up engagement.
Pricing and what ships with every project
New brand launches typically fit the Websites Business tier, starting at $7,999 fixed-price for 8–12 pages with CMS and analytics. The Starter tier at $2,999 covers leaner launches: five or six pages, simpler design, lighter CMS. The Corporate tier at $11,999 fits deeper IA, multi-language, or complex third-party integrations.
Every project ships with the 14-day money-back guarantee and the 1-year bug warranty — if something I built breaks, I fix it at no charge. Work Made for Hire means you own everything: the code, the Figma files, the CMS configuration, the deployment setup. Nothing lives on my accounts after handover.
Most founders continue on a lighter post-launch engagement for the first three to six months while marketing hires ramp up. That is smaller than a full retainer — just ongoing content additions, new pages, or minor design updates as your story evolves.
Recent proof
A comparable engagement, delivered and documented.
Built and shipped an investor-ready MVP from scratch
Built the entire technological base and delivered MVP in just 3 weeks, enabling a successful rapid launch and investor demo.
Read the case studyKeep reading
Frequently asked questions
The questions prospects ask before they book.
On standard 8–12 page brand sites with a decided positioning and basic brand direction, yes. The timeline risk lives in the inputs: slow copy approvals or brand decisions that get re-opened push the schedule. I share daily async status so you can see exactly which decision is on the critical path and act on it. The GigEasy build — marketing site plus MVP platform — shipped in 3 weeks on that same rhythm.
For copy, I draft the site from a 90-minute positioning workshop plus your pitch deck and a recorded founder interview. You review and approve, not write from scratch. For brand, I can work from a basic logo and type direction. Full identity work — wordmark, full system, brand guidelines — is outside scope, though I can point you to designers I trust if you need it.
Five to seven pages covers almost every seed-stage scenario: homepage, about, product or service, careers, contact, and a blog scaffold. Anything beyond that is usually premature and delays launch. I build the URL structure and component system to support ten or fifteen pages at Series A, so adding them later is additive, not architectural.
It depends on who edits the site in the next 12 months. Sanity for marketing-heavy teams publishing content at volume; Contentful for larger editorial teams; Notion for lean founder-only editing; MDX in the repo for engineering-led teams. I walk through this decision in the kickoff call — the answer changes based on your hiring roadmap, not personal preference.
The site ships with clean URL structure, semantic HTML, structured data (Organization, WebSite), a sitemap, and a robots.txt. Meta titles and descriptions are set for every page. Core Web Vitals pass before DNS flip. That is the technical foundation; content strategy and keyword targeting are a separate engagement after you have the site live.
Every site ships on Vercel — production-grade, CDN-backed, and predictably priced as you scale. I handle DNS on launch day regardless of where your domain is registered. You own the Vercel project and the repository from day one. After handover, your team can deploy by pushing to main — no vendor lock-in, no mystery infrastructure.
The 1-year bug warranty covers anything that breaks in what I built, at no charge. Beyond that, I offer a lighter post-launch engagement — ongoing content additions, new pages, and minor design updates — sized below the full retainer. Most founders use it for the first three to six months while a marketing hire gets up to speed.