Warling Dev: a professional services site

Anyone selling technical services by referral faces the same problem repeatedly: every prospect arrives without knowing exactly what's offered, what the process is, or what happens after they say yes.

With no site where that's written down, it gets explained live. Every conversation starts from zero, with the same questions and the same answers. That's unbilled time, repeated with each person.

There's a less obvious cost too: without a presence of your own, the person recommending you has nothing to send. The referral arrives as a phone number and a «he knows his stuff», which is far weaker than a link.

The site loads in under two seconds and explains services and process so he doesn't have to repeat them in every conversation. People arriving by referral already know how he works, and the first call starts where it used to end.

It's the smallest of the three cases and probably the most replicable: most service professionals are in exactly this situation.

A developer who ships slow sites has a credibility problem no copy can fix. In this case the site is itself a sample of the work.

So speed was measured rather than promised. It's the same standard we hold ourselves to: if we're going to say we build fast sites, ours has to survive someone checking.

No blog, no extensive portfolio, no testimonials section. All three are good elements when you have something to fill them with, and none of them are when you don't.

An empty blog whose last post is two years old signals abandonment. A testimonials section with two unattributed lines signals there weren't any more. We preferred a short site that says what exists over a long one with half-filled sections.

Growing later is easy: the structure is already prepared to add those pieces once there's real material for them.

Nearly all of it. A lawyer, an accountant or an architect working by referral has exactly the same problem: explaining the same thing in every conversation, with nothing for referrers to send.

The structure that worked here — services explained one by one, a visible process, and a single path to contact — is the same one we use for consultancies. The content changes, the skeleton doesn't.