Starting Sparrow Group: From Writing Code to Running the Business

When I started Sparrow Group, coding was the area I knew best. Sales, taxes and the administrative side of running a business were less familiar. A working website was a problem I understood how to approach. Running the business around that work brought a different set of questions.

What exactly was I offering? What would the customer need to provide? Which decisions belonged in the proposal, and which could wait until we had something to look at?

Those questions deserve more than the usual advice to believe in yourself and keep going. This is the part of starting a web business I want to explain: how the responsibility grows beyond the code.

A website project starts before the first page

A developer can look at a request and begin picturing the implementation. The customer may still be deciding what the website should help someone do.

Take a home-plan catalog. A visitor might want to compare plans, inspect a particular layout or open a floor-plan document. Those are related tasks, but they call for different pieces of the website. A handsome opening photograph cannot do all three jobs.

That example is grounded in work readers can inspect. Poteet was my first customer, and we still work together remotely. Today, the relationship includes the Poteet Homes and Texas Luxury Builder websites, with work on home plans and property listings. The Poteet project page shows the website in more detail.

The continuing relationship is a fact about the work. It is not a claim about how many homes the website sold. That would require a different kind of evidence.

Learning the business means making the offer understandable

The person buying a website should not need to translate a developer's assumptions into an agreement.

Consider the phrase “keep the website updated.” It sounds reassuring, but it leaves almost everything open. Does it mean replacing a photograph? Adding a new service page? Building an inventory system? Who supplies the new information? What happens when the requested change needs a different layout?

The useful work is to make those distinctions visible before they turn into disappointment. Sparrow's website plans explain the current allowances, responsibilities and terms. They are the place to check what a new proposal includes; an early founder article cannot substitute for the current agreement.

I still care about how the code is written. The business part is making sure the customer can understand the work they are asking me to do.

Books can help you recognize a question

In the first version of this article, published in February 2024, I encouraged people starting a business to build on their strengths and keep learning through books, online resources and mentorship. That remains a useful starting point.

The limit is that reading about a decision does not make it for you. A book can explain why a business should understand its customers. It cannot tell you which unanswered question is stopping someone from using your particular website.

For that, look at something concrete: a service description, an inquiry form, a proposal or a customer question. Ask what you know, what you have assumed, and what evidence could change your mind. Learning becomes useful when it changes how you approach the next piece of work.

Launch is one moment in the relationship

A website can be complete enough to launch and still need attention later. Services change. A property is listed or sold. A photograph is replaced. An old explanation stops matching the business.

That is one reason the ongoing work matters to me. The launch is visible, but the less dramatic changes help keep the site useful and accurate. They also need a defined scope. Routine content work and a new custom feature are different requests, even if both begin with “could you change something on the website?”

What I want you to be able to judge

I run Sparrow Group, and we build websites for small businesses. You can inspect the project work, read the current terms and ask about the decisions behind a proposed site.

You do not have to take a founder story as proof that a particular project is right for you. Bring the practical question: what should a visitor be able to find out or do, and where is the current website getting in the way?

Send me the background on your website. A specific page or task gives us a useful place to start.