I need something online this week

Somebody asked for your website and you don't have one. Maybe it's a conference in six days and the badge template wants a URL. Maybe it's a client who asked for an invoice with a website on it, which is a strange thing to require and also completely normal. Maybe it's an introduction on Friday and you'd rather send a link than a paragraph about yourself. Whatever the trigger, the honest version of the question isn't "how do I build a website" — it's "how do I get something real online in the next five working days without it looking like it was built in five working days."

The advice aimed at that question is usually bad advice repackaged from the advice aimed at a different question — the person with no deadline who's deciding whether to build a personal site at all. That person can afford to explore fonts, write three versions of an About paragraph, and let the project stretch across a month of evenings. You can't, and pretending otherwise is how a week under pressure turns into a half-built page with two empty sections and a broken nav link, which is worse than the paragraph you would have sent instead. The honest starting point concedes that: a rushed site is often worse than no site. What changes that outcome isn't more hours. It's cutting scope hard enough, on day one, that everything you do afterward fits inside the time you actually have.

Cut the scope before you cut anything else

The single decision that determines whether this works is made in the first hour, not the last: one page, one message, three proofs.

One page, because a site tree is a maintenance project and you don't have a week to maintain anything — you have a week to ship it. A second page is the first thing that goes unfinished, and an unfinished second page reads worse than no second page. We've made the general case for this trade-off in one-page versus multi-page personal sites; under a deadline the case stops being general and becomes the only option worth considering.

One message, because a page trying to say "I do consulting, and I'm also open to full-time roles, and I also have a side project worth mentioning" says none of those things. Pick the one a stranger needs to understand in the first ten seconds — what you do, for whom — and let everything else be a supporting detail rather than a competing headline.

Three proofs, because a claim needs evidence and three is enough. Three projects, three clients, three pieces of work you'd point to if someone asked "show me." Not ten, because picking ten takes longer than picking three and a visitor won't read past the fourth anyway. Not one, because one looks like luck. Three is the number that fits a single scroll and still argues something.

Everything else — the tagline that captures your whole philosophy, the testimonials, the blog you'll definitely start — gets written down on a list titled "not this week" and left there. We go into why a page needs a clear job before it needs anything else in what a personal website is actually for; under a deadline that job reduces to exactly the three things above.

The two things that will eat your week if you let them

Two decisions expand to fill however much time you give them, and neither is the one that actually matters.

The first is choosing a look. There is no objectively correct font pairing, and if you go looking for one you will still be looking on Thursday. Give yourself thirty minutes, pick something legible and not embarrassing, and move on. The look is not what gets you hired or introduced; the words are, and the words are what people actually spend their attention on.

The second is buying a domain. Checking availability, comparing three registrars, deciding between the .com that's taken and the .io that isn't — this can consume an entire evening and it changes nothing about whether the page does its job by Friday. A domain is a decision you're allowed to make later, once the page exists and you know the name is one you actually want attached to it long-term.

Time sink	Reasonable budget	What happens if you don't cap it
Choosing colors and fonts	30 minutes	You're still comparing on day four
Buying and configuring a domain	Deferred to week two	Nothing else gets built while DNS propagates
Writing the words on the page	The rest of the week	This is where the time should actually go

The words are where a rushed page fails, not the design. A visitor forgives a plain layout. They don't forgive a paragraph that hedges, rambles, or says nothing specific about what you do. Whatever time you save by timeboxing the first two rows, spend on the third.

A draft beats a blank page, every time

The single biggest obstacle in a compressed timeline isn't taste, it's the empty canvas — the moment where you open a page builder, see a blinking cursor over a hero section, and have to invent a headline from nothing. That moment is where most personal sites actually die, not because the person lacks the skill to finish one but because starting from zero words is a much harder task than editing fifty.

This is the specific problem reach is built to remove, and it's worth being concrete about what it does rather than vague about how fast it feels. You upload a CV and a photo, answer a short profile form, and pick a look — six background presets, six accents, or your own colors, and a set of hero layouts filtered to your role. The page itself is generated in about twenty seconds, and you can be live at a free yourname.joinreach.app subdomain in under two minutes, counting the time you spend filling in the form. What changes under a deadline isn't the speed by itself — it's that the task in front of you is now "is this draft right," which is a much smaller question than "what do I even say," and it's the second question that actually costs a week.

The reason the result holds together isn't that it's picking from a shared gallery the way a template picker does. The layout is assembled from a large set of vetted sections — twenty hero layouts across five design families, for a start — filled with copy written specifically from the CV you gave it, not filler text you'd replace by hand. That's the difference between starting from a draft and starting from a placeholder.

Know what you're giving up before you commit

None of that is free of trade-offs, and they're worth knowing on day one rather than discovering them on day five with no time left to route around them.

It's genuinely one page — a single index.html, no sub-pages, no site navigation — which is fine here because one page is what you decided to build anyway. But there's no contact form; the contact section is a mail link and your profile links, not something that posts to an inbox or a CRM. There's no visitor analytics built in, so you won't know who looked at the page unless you add that yourself later. There's no HTML export and no custom code field, so you can't take the markup somewhere else if you outgrow the tool. And the editor itself needs a desktop screen — below about 820 pixels wide it drops to a read-only preview with a share link, so drafting on your phone on the train works for looking, not for editing.

None of that should surprise you in week two if you read it in week one. It's a real constraint for some jobs — an agency site, a shop, anything needing a form wired to a database — and the right shape for the job in front of you this week, which is a page, not a platform.

Publish to the subdomain now, buy the domain when you're ready

If a custom domain isn't going to resolve before Friday, don't wait for it. A free subdomain is instant — no cost, live as soon as you publish — while a custom domain depends on registrar DNS and a certificate, which takes minutes to hours after payment even in the best case. That gap is exactly the kind of thing a deadline can't absorb.

Publish to the subdomain, put that link on the badge or in the signature, and treat the domain as a week-two task once you're sure the page and the name are ones you want to keep. A custom domain through reach costs $4.99 a month or $49 a year on the Premium plan; if you're already committed to the name, buying it early and letting the DNS settle in the background costs nothing but patience. Prices checked August 2026.

If your material already lives somewhere else — a Notion workspace you've kept up for months, say — publishing that directly can be the faster route for you specifically, and we cover that version of this decision in using Notion as a personal website. The CV-to-page route above assumes you're starting from a résumé, not an existing page.

What to leave deliberately unfinished

A week-one page should have visible gaps, not hidden ones. Decide now, in writing if it helps, what you're not doing yet: no second page, no blog, no case-study write-ups beyond a sentence per proof, no custom domain, no contact form beyond the mail link. Put a date on when you'll revisit it — two weeks out is realistic — and then stop thinking about those items until then.

The mistake under a deadline isn't shipping something incomplete. It's not deciding, on purpose, which parts are incomplete — and then noticing halfway through the week that you're polishing a font choice while the actual proof-of-work section still says "coming soon."