Running a Software Firm That Creates Client Value
Software only creates value when a client can see it in their business: more sales, less admin, fewer errors, better decisions. Code that ships on time but changes nothing is a cost, not an asset.
At James Anthony Consulting (JAC) we have spent years refining how we run an Adelaide software firm so that every project leads back to a result our clients can point to. Our internal management framework, project management handbook and weekly rhythms all grew out of that one goal. Here are the practices that matter most.
1. Start with the problem, not the feature list
Clients rarely arrive with a tidy specification. They arrive with "I think this app would work for us", "our last developer left us in a mess" or "I need to sell more of these". Each of those is a different job, and the first task is working out which one you have been handed.
We don't expect clients to manage the project carefully. We expect them to understand their own business drivers and goals, which we then articulate back to them to check and confirm. If something they say makes no sense to us, we ask until it does. Admitting you don't understand is a sign of honesty, not weakness.
Before any build starts, our project managers work through a simple test we call "Is it safe to start the project?" Every answer must be yes:
Is there a named user representative who will be available every week?
Is there a clearly identified client who is paying for the work?
Is there a written scope, and has the client approved it?
Has a senior technical lead reviewed the architecture?
Can the project manager see a path to finish, start to end, even if not the perfect one?
Have the risks been noted, with a plan for each?
Does the client understand their role in testing?
Do we understand the client's timeframe and what happens if it slips?
A single missed item can sink a project, so the goal is to clear all of them quickly during pre-sales and design, not halfway through the build.
2. Wrap agile in a business case
Agile is excellent for speed and adapting to change. Left on its own, though, it can drift into "runaway development" that consumes budget without proving a business result. Agile is user-obsessed; it was not designed to show a business owner a return.
We wrap our agile delivery inside a V-model that extends all the way up to the business case. In practice that means:
Every project has Key Objectives, a Requirements Register and an Issues Register from day one.
At regular checkpoints we test the work against those objectives, not just against user stories.
We decide deliberately when to go deep on verification and when a light agile touch is enough.
The same discipline applies to price. Quotes should be accurate, appropriately detailed and timely. Any quote request gets a same-day reply with our terms, a ballpark figure and the key factors we are weighing. We are realistic about what we offer and about the client's budget appetite, and we resist the temptation to win work by cutting price. Finding the words to justify value serves both sides better.
3. Keep the client inside the story
The single most important habit in our business is the weekly written status update. Every active project gets one, without exception, and project managers don't finish their week until they are sent. An informed client is a confident client, and a confident client stays with you.
A good update is more than a task list. It maintains the business narrative of the project: what has happened, what will happen next, and when the client can expect it. We measure completion at least weekly so the client always knows the answer to "when?"
A few rules make this work:
Bad news travels early. If the schedule, budget or quality is at risk, we raise it immediately, internally and then with the client. We never break bad news for the first time in a routine report.
Make progress visible. When a client gets anxious about timing, we give them a measure they can watch fall, such as "X issues tracked, Y fixed, Z remaining".
Talk, don't just email. We speak with every client at least fortnightly, and we bring the program or schedule to every meeting.
Be responsive. Every email is at least acknowledged the same day. Quote requests, complaints and security incidents get a real answer the same day. Many IT firms are poor at this, which makes it a genuine advantage.
We also read clients carefully. Some want to collaborate and be across every decision. Others want to delegate entirely and expect us to sort it out. Recognising which one you are working with shapes how much detail they receive and when we make a call on their behalf.
4. Run delivery on a steady rhythm
Client value depends on predictable delivery, and predictable delivery depends on rhythm. Our framework treats the business as a set of pipelines (prospecting, quoting, delivery, invoicing, support and strategy), each with a clear owner, regular routines and measurable indicators.
On the delivery side, that rhythm looks like this:
A weekly capacity plan. Project managers bid for the people their projects need, and clashes are resolved in one meeting before the week starts.
Daily standups and weekly project reviews. Developers get clear written briefs on day one of each task, and the project manager walks through the actual product every week.
Minimum launch testing on every release. Every form and every checkout gets tested, every time, and security checks form part of go-live.
Rolling go-live dates. Rather than one high-stakes launch day, we book several candidate dates and ask "are we ready?" on each.
Planned handovers. When a project changes hands, the incoming manager drives a structured handover and sits in on the next three client meetings, so the client never feels the change.
We also keep a healthy ratio of roughly one project manager to five technical staff, with managers who engage with the detail. That ratio is what allows managers to understand the product well enough to protect the client's interests.
5. Think for your clients after launch
Launch is where value starts to be proven, not where the relationship ends. One of our guiding principles is that we think for our clients without being asked: we are proactive and we offer to help.
Keep systems live and secure. Supported systems have an assigned owner, routine patching and a regular maintenance report.
Spot the next step. Project managers look out for phase twos and improvements, and raise them promptly. A client who asks for more work should never wait on a quote because the team feels busy.
Listen to users. Their feedback and insights are among our best sources of quality improvement.
Don't cookie-cutter. Every project has unique challenges, even when it resembles a past one, but we carry forward everything we learned last time.
The measure we care about most is simple: clients who seek us out again. Integrity means both sides should win from every project, and repeat work is the clearest sign that they did.
The short version
Creating client value isn't a single technique. It's a set of habits practised every week:
Understand the business problem before writing code.
Tie agile delivery back to a business case and an honest price.
Communicate weekly, and deliver bad news early.
Run delivery on a predictable rhythm with real quality gates.
Stay proactive after launch.
As one line in our framework puts it: we help our clients win in ways they can see.
If you have a digital project in mind, an existing system that needs a steady pair of hands, a troubled project that needs rescuing, or a platform due for a security audit, we'd love to hear from you. Get in touch with our friendly team.
