The DIY Website Time Audit

Every guide who has built their own site underestimated it, and they all underestimated it the same way. They budgeted for the website work and the website work was never the problem. Dragging blocks around a page is quick, genuinely quick, and the platforms have spent a decade making it quicker. What consumed the weekends was choosing which trips to list, writing sentences about a river they know perfectly well and cannot describe, finding a photograph in which nobody is squinting, and deciding what a half day actually costs. None of that is website work. All of it is required before a website can exist.

Why is the estimate always wrong in the same direction?

Because people estimate the visible task. Building a website looks like arranging pages, so that is what gets budgeted, and the invisible prerequisites arrive as surprises one at a time.

The surprises are all decisions. What is the minimum age on the flats trip. Do you run half days in October. Is gear included or extra. Each of those takes ten minutes to decide and has been deferred for three years because nothing forced it.

A website forces them all at once, which is genuinely useful and completely unbudgeted. That is why the work feels harder than it looks and why it stalls in the same place every time.

The practical consequence is that a time audit measuring hours in the site builder measures the smallest component. What each page needs to say is set out in the page list.

The Reef, WY

How do you audit it honestly?

Log the hours as you spend them, in four buckets, rather than reconstructing afterwards. Deciding, writing, images, and assembly. The split is the finding.

Most guides who do this discover assembly is well under a quarter of the total. The other three quarters is work that would have been required whoever built the site.

That changes what the audit is for. It is not measuring whether you should have hired somebody; it is measuring how much of the job was ever transferable.

Keep the log even if you abandon the project halfway. A partial log with a stalling point in it is more useful than a complete one, because the stalling point is the finding.

Record the calendar time alongside the hours, because the two diverge wildly and the gap is informative. Nine hours spread over eleven weeks is a different situation from nine hours across two Saturdays, and only the first one is a problem.

What that gap measures is how often the work got interrupted by something it could not proceed without. Each of those is a decision you had not made, and the list of them is the real project plan.

Write those interruptions down as they happen rather than working around them silently. By the end you will have an inventory of everything the business had never settled, which is worth more than the website.

What actually stalls people?

The writing, at the trip descriptions specifically. It is the point where a site goes from seventy percent finished to abandoned, and it happens because the task is misdescribed.

Guides think they are being asked to write marketing copy, which is a skill they do not have and do not want. What is actually needed is a description of the day, which they could give out loud to somebody at a ramp without hesitating.

So change the task rather than pushing through it. Speak the description into a phone, answering what the day involves and who it suits, then transcribe and cut. The register arrives free that way.

The same substitution works for the about page, and for the same reason: you would never say the phrases you are tempted to write, which is the argument in the bio piece.

How long does the assembly genuinely take?

Less than a working day for a small site if the inputs exist, which is the part that surprises people once they get there. Modern platforms are built for exactly this.

The platform itself is a small commitment. A mid-tier plan runs $29 a month on annual billing, on a ladder from $19 to $99, and the pricing page notes that paying monthly costs up to 36 percent more than the annual rates shown.

Google's own guidance on hiring for search work says something similar about the wider job: a small local business can probably do much of it without help, and appearing in organic results carries no fee.

So the assembly barrier is low and getting lower. The barrier that has not moved at all is having something specific to assemble, which is the point of this whole article.

What about the checking, which nobody budgets for?

Roughly an hour, once, and it is the difference between a site that works and one that appears to. Most of it is mechanical and none of it needs skill.

Twenty minutes covers the accessibility pass. The Justice Department's guidance names the barriers to look for, including forms without labels or error messages, information carried by colour alone, and navigation that requires a mouse.

Its warning about tools is worth carrying into this hour. A clean report from an automated checker does not mean everything is accessible, and it recommends pairing manual checking with automated results rather than trusting either alone.

The rest of the hour is the mechanical tests: submit your own form from a handset off wifi, ring your own listed number, and load a page on a weak signal. Each one catches a failure that is otherwise invisible from your desk.

What takes longer than anybody expects?

Photographs, and not because of editing. Choosing them is the slow part, and choosing is a judgement call you make several hundred times.

A season's camera roll is thousands of frames, most of which are somebody holding a fish. Finding twelve that show different things, in different light, with faces visible, is an evening of scrolling.

Resizing them afterwards is fast and mechanical, and it is the part people dread. The dread is misplaced: the sorting is the work.

Shooting deliberately through a season removes almost all of it, because you arrive at the site with a set rather than an archive. What to shoot, and who owns it, is covered in the photos piece.

What does the audit tell you about hiring?

Less than you would hope, and that is the honest finding. Paying somebody removes the assembly hours and the checking hours, which are the small ones, and leaves the decisions and the writing with you.

A builder cannot decide your minimum age or write a true sentence about your water. Those inputs get supplied by you or they get replaced by generic material, and the second outcome is what a fast build produces.

So the honest comparison is not your total hours against a fee. It is your assembly and checking hours against a fee, with the rest of your time appearing on both sides of the ledger.

That is a much smaller number than most DIY-versus-hired arguments assume, in both directions. The full three-year comparison, with both columns priced, is in the ownership cost piece.

What is the cost of not finishing?

The one cost nobody enters in the ledger, and for DIY it is the dominant risk. A site stuck at seventy percent since March charges you a subscription every month and, more expensively, everything the completed version would have brought in.

Half-built sites are common and they fail in a predictable place. The structure is up, the pages exist, and the trip descriptions say lorem ipsum or a placeholder sentence nobody replaced.

If you have started and abandoned this before, that is real information about the next attempt rather than a character flaw. It is also a legitimate reason to pay somebody, which is a better use of self-knowledge than a resolution, and what that purchase does and does not include is set out in the fast builds piece.

The other legitimate response is to shrink the project. A four-page site that is finished beats a nine-page site that is not, by an enormous margin.

How do you make the time smaller?

Do the decisions and the writing before opening any site builder. That single change removes most of the stalling, because the builder then becomes assembly rather than a place where you discover unanswered questions.

Work from paper or a notes app. Which trips, how long, what they cost, who they suit, what people always ask. An evening of that is worth three evenings inside a builder.

Then batch the assembly into one sitting rather than spreading it. The context cost of returning to a half-built page repeatedly is real, and it is what turns a day of work into six weeks of Sunday evenings.

Winter is when both halves are possible, and the reason to do it then rather than in spring is that neither half competes with a season. The full argument is in the offseason piece.

One more thing shrinks it, and it is the least obvious. Decide in advance what you are not doing. A blog, a gallery page, a conditions feed and a newsletter signup are each a small amount of assembly and a large amount of deferred obligation.

Writing that exclusion list down converts a vague sense of an unfinished site into a finished one. The pages you deliberately did not build are not gaps; they are decisions, and decisions do not nag.

Revisit the list once a year rather than never. Something on it may have earned its place by then, and something already built may have earned removal, which is the same annual pass everything else on the site gets.

R.R. 406, MT

What does maintenance actually cost per year?

Less than the build and more than nothing, and the honest answer is that it depends entirely on whether anything changed in the business. A season where you sold a boat costs more than one where nothing moved.

The recurring part is small: a check that the form still delivers, that the number still rings, and that nothing on the page has stopped being true. How to find what has quietly stopped being true is set out in the staleness piece.

The variable part is whatever the season produced. New photographs, a rate change, a trip you dropped, a question people started asking that the site does not answer.

Budget an evening a year for the recurring part and treat the variable part as it arises, which is how a maintained site avoids becoming a rebuild. Which of those changes actually matter is sorted in the rebuild piece.

Does using a generator change the arithmetic?

It shrinks the smallest bucket further and leaves the other three alone, which is the same shape as hiring somebody. Assembly gets faster; the decisions and the writing do not move.

Generated copy in particular is worth understanding rather than dismissing. It produces fluent, plausible sentences about guided fishing, and fluent plausible sentences about guided fishing are exactly what the reader has already seen on every other site.

Where it genuinely saves time is structure and first drafts of the parts that are the same everywhere. An outline, a cancellation policy, a what-to-bring list.

Where it costs you is anything whose value is specificity. A sentence about your water is worth writing badly yourself rather than well by something that has never seen it.

What is the smallest site that actually works?

Four pages, and naming that is the most useful thing in this article for anybody who has stalled. Home, trips, about, contact. Everything else is optional and can wait a year.

Shrinking the project is the only reliable way to finish it, and finishing is what determines whether any of the hours produced anything. A live four-page site takes bookings; a nine-page draft does not.

The four pages also happen to carry all four jobs a guide site has to do. Somebody can find the price, book from a phone, see who runs the operation, and get an answer quickly.

Add pages afterwards from evidence rather than from a plan. A question people keep asking earns a page; a page you thought you should have does not, which is the same reasoning applied to trips in the trip pages piece.

There is a second advantage to starting small that only shows up later. A four-page site is one you can hold in your head, which means you will actually maintain it, and a site that gets maintained beats a larger one that quietly drifts out of date.

What do experienced guides do differently?

They log the hours the first time round, because that log is what makes every later decision easy. And they separate deciding from building rather than doing both at once.

The log costs nothing and cannot be reconstructed. A guide who knows their first build took fifty-two hours, of which nine were assembly, can evaluate any quote in about a minute.

The separation habit is the one that saves the most time. Deciding and building are different modes, and switching between them constantly is why a task that contains one working day of assembly takes a month.

Experienced operators also finish before improving. A live site with plain descriptions beats a beautiful half-built one, and the improvements are easier to judge once the thing is in front of real visitors.

What are the common mistakes?

Budgeting for assembly only. Opening the builder before the decisions are made. Spreading the work across months. And treating an abandoned attempt as a reason to try the same way again.

The assembly-only budget is what produces the universal underestimate this article opened with. It is not a failure of discipline; the visible task genuinely is small.

The spreading mistake is the one that compounds. Every return to a half-built page costs re-orientation, and six Sunday evenings contain far less work than one Saturday.

The repeat-attempt mistake is worth naming gently. If the same project stalled at the same point twice, the fix is a different approach rather than more resolve, and paying for assembly while keeping the writing is a perfectly reasonable middle. More on that split sits on the guide websites hub.

What surprises people?

That assembly is under a quarter of the time. That the writing stalls more projects than anything technical. And that most of the hours would have been spent whoever built it.

The last point is the one that reframes the whole hiring question. If three quarters of the work is inputs only you can supply, then the choice is not between doing it and not doing it, but between doing three quarters and doing all of it.

That is a much smaller decision than it usually feels, and it is a considerably cheaper one to get wrong in either direction.