I work as a small development coordinator for landlords and private owners across Northamptonshire, Bedfordshire, and the edge of Cambridgeshire. Most of my week is spent checking sites, speaking with trades, reading planning notes, and helping clients decide which builder or developer is worth a proper conversation. A company website never gives me the whole answer, but it usually tells me enough to know whether I should make the call or move on.

The first things I check before making contact

I always start with the tone of the site. I am not looking for fancy words or a polished sales pitch, because plenty of good firms have plain websites and plenty of weak firms have beautiful ones. What I want to see is whether the business explains what it actually does without making me guess. That sounds basic, but I have seen enough vague building websites to know it is not automatic.

The first 5 minutes matter. I look for the type of work they handle, the areas they cover, and whether their past projects feel close to the kind of job sitting on my desk. A small infill build behind a row of terraces is a very different animal from a large rural plot, even if both end up being called residential development. If a site helps me sort that difference quickly, I take it more seriously.

I also pay attention to how much confidence the site gives me before I speak to anyone. Last autumn, a client asked me to shortlist firms for a tired building with awkward access and a narrow frontage. Two companies had nice project photos, but only one gave enough context about the way they approached development work. I called that one first because I could already picture the first conversation.

Reading past the front page

The front page is usually the least useful page for me. It tells me how the company wants to be seen, while the inner pages tell me how much care they put into explaining their work. I usually spend more time on project pages, service pages, and the contact page than I do on the opening screen. Small clues add up quickly.

For a client who wanted a measured first look at a local development firm, I pointed them toward the wickstead website because it gave them a place to start before arranging a proper discussion. I still told them to ask direct questions, because a website is a doorway rather than a handshake. The useful part was that they could read through the company’s own presentation first and come into the call with 3 or 4 sensible points ready.

I like websites that make contact simple without pushing too hard. If I have to hunt through 6 pages to find a phone number or basic enquiry route, I start wondering what the rest of the process will feel like. That may sound harsh, but building projects already contain enough friction. A clear website does not remove the hard parts, yet it can show that the company respects people’s time.

There is also a difference between a site that looks expensive and a site that feels useful. I worked with a retired couple last spring who cared less about glossy images and more about knowing who they might be dealing with. They had saved for years to improve a small plot attached to their home, so trust mattered more than decoration. I told them to read the wording slowly and note any questions that came up twice.

How I judge whether the company fits the job

I never treat one website as proof that a company is right for a project. I treat it as the first filter. If a site suggests the firm works on the same scale, in the same general region, and with the same kind of property issues I am dealing with, then I move it to my call list. On a normal week, that list might start with 8 names and end with 3 serious conversations.

The fit matters more than size. I have seen small firms handle complicated builds with calm discipline, and I have seen bigger outfits struggle because the job did not suit their usual rhythm. One narrow-site project I helped with had parking pressure, neighbour concerns, and delivery restrictions before the first skip arrived. A developer who understands those headaches is worth more than a firm that only talks about finished photographs.

I also look for signs that the company knows the local development process. Planning, drainage, access, and existing services can shape the whole job before anyone talks about finishes. A website will rarely explain all of that in detail, and I do not expect it to. I just want enough evidence that the firm is used to projects where the paperwork and site conditions are as real as the brickwork.

Photos help, but I do not let them lead the decision. A bright kitchen or clean exterior shot can hide a messy build process, while a plain project photo might represent a job that was run with real care. I usually ask myself one question while looking through project material: would I trust this company to talk plainly about a problem on week 9? That question has saved me from a few bad matches.

What a good website still cannot tell me

No website can show me how a firm behaves when rain delays the groundwork or a supplier sends the wrong windows. That is where phone calls, references, and early meetings still matter. I have had projects where the first call told me more than 20 pages of online copy. People reveal a lot in how they answer simple questions.

I ask practical questions early. Who manages the day-to-day contact? How do they handle changes once work has started? What kind of information do they need from the owner before giving a meaningful response? If the answers are vague, I slow the process down.

A good website can make me comfortable enough to start a conversation, but it cannot replace judgement. I still want to know how a company prices risk, how it talks about timelines, and whether it admits the awkward parts of a build before the contract is signed. A firm that is honest about limits usually gives me more confidence than one that makes every job sound simple. Nobody builds well by pretending problems never appear.

I remember one landlord who nearly chose a contractor based only on a smart website and a quick reply. After a longer call, it became clear that the firm was set up for lighter refurbishment work rather than the heavier structural changes the building needed. The website had not lied, but it had not carried the full story either. That is why I treat online research as the start of the work, not the decision itself.

The notes I keep after reviewing a developer online

I keep a short page of notes for each company I consider. It is nothing fancy, just the kind of working record I can read back before a meeting or share with a client. I usually write down the service fit, the location fit, the questions I still have, and anything that made me pause. Four lines can be enough.

The pause points matter. If a site avoids detail, I write that down. If the projects shown feel larger or smaller than the job I am handling, I write that down too. These notes stop me from being swayed by one good photo or one smooth sentence.

I also record the first human response. A helpful call, a clear email, or a sensible request for drawings tells me the website was backed by a real process. Silence for several days does not always mean a company is poor, because good firms get busy, but it changes how I advise a client. On live projects, slow communication can cost several thousand pounds without anyone meaning for it to happen.

For me, the best way to use the Wickstead website is to read it with a builder’s caution and a client’s curiosity. I would look at what the company says, compare it with the job in front of me, and then ask direct questions before making any commitment. That keeps the website in its proper place, useful, practical, and only one part of a much bigger decision.