INDEPENDENT BUSINESS RESEARCH FOR SOFTWARE DEVELOPERS WORKING WITH SMEs

The system you built is not the whole business.

You know the system, the people and the work it was built to support. But an SME makes other decisions that may never become a software request.

I compare what you built with how the client earns money, delivers work and manages obligations. If the available evidence supports it, I give you one specific business question to validate with the client. If it does not, I say so.

One selected client · Your non-confidential project context + public evidence · Written note · 1 working day after agreed inputs and payment

THE SITUATION

You have the relationship. What is the next question worth asking?

The client only asks for fixes and small changes.

You maintain their system, but substantial new work rarely comes up. You want a reason to discuss the wider business, not another feature pitch.

The original project had a defined scope.

That scope was agreed with particular people for a particular purpose. It does not establish which decisions elsewhere in the business are already well supported.

Your skills extend beyond the current system.

A bigger project needs a business reason, not a longer list of things you could code.

Not a lead-generation service. The Account Screen starts with a client you already know. If they have an agreed new requirement, proceed with your normal discovery.

WHY OPPORTUNITIES GO UNSEEN

A working system can fulfil its brief without covering every business decision.

A small company may manage decisions across its owner, staff, spreadsheets and several applications. A project brief captures the decisions that were in scope and the people involved. An adjacent activity may never have been considered — even if the delivered system works well.

Map the business activity

What does the client offer, what does it promise, and what work follows from each promise?

Define the system boundary

Which tasks, records, decisions and users did your project actually cover?

Identify adjacent decisions

Which decisions rely on information or authority outside that boundary?

Check evidence and alternatives

What is publicly supported, what remains unknown and what would rule the idea out?

HOW THE SCREEN WORKS

A second perspective on a client you already know.

You explain the purpose and scope of the work you delivered. I research the wider business using public information. The written result tells you whether there is sufficient evidence for a further client conversation.

YOU SUPPLY

One client and project context

The client's website and a non-confidential account of the system or work you delivered.

I ASSESS

Business context beyond that scope

Whether the available evidence gives a credible reason to explore a question outside the original assignment.

YOU RECEIVE

A written decision

The supporting evidence, a suggested next conversation where justified, or a reason not to pursue one.

No access to your code or client systems. No contact with your client. An inconclusive or negative finding is a valid result.

A DIFFERENT KIND OF RESEARCH

A new project starts only if the business question survives a real conversation.

A system can fulfil its brief while other parts of the business operate under different requirements, information flows or decision rights. That does not mean anything is missing. It means the original assignment cannot, by itself, settle what else may be worth discussing.

The Screen distinguishes a supported reason for a conversation from an untested idea. It does not produce a software specification, a list of features or a qualified sales opportunity.

WHAT YOU RECEIVE

A sourced conclusion on whether to start another conversation.

BUSINESS CONTEXTWhat the client's business model suggests

What is known: dated public sources and the original project scope you describe.

POSSIBLE GAPWhat may sit outside the original brief

What might follow: the adjacent business decision, likely data or responsibility boundaries and alternative explanations.

DECISIONWhat would need checking next

What to ask the client, what would disprove the hypothesis and whether to investigate or stop.

See the deliverable and limits ↗

WHO IT IS FOR

For people who build business systems and keep working with the client.

The clearest fit is a freelance or independent developer who builds and maintains business applications for SME clients: internal tools, CRMs, databases, workflow automations or integrations. There is no required programming language or software stack.

PRIMARY FOCUS

Independent software developers

You own the client relationship and do the development. I investigate business questions that may not have appeared in the brief.

For independent developers

ALSO RELEVANT

CRM & IT implementation specialists

Work on the existing system may not show the decisions and information needs elsewhere in a client's business.

For CRM partners

TWO SEPARATE SERVICES

Start small, or come with a defined question.

FIXED PRELIMINARY REVIEW

Account Screen

£50

1 working day after agreed information and payment

One selected SME client. A short, sourced assessment of a business question that might warrant further investigation.

Enquire about a Screen ↗
SCOPED INVESTIGATION

Further account research

£350–£1,500

Indicative fees · written quotation

Examine a defined question and competing explanations in greater depth. You can commission this directly, without a Screen.

Scope and quotation

The £50 Screen stands alone. If you commission further research on the same account, the £50 fee is credited in full. Neither service guarantees a new project or a revenue outcome.

Have a client you would like to understand beyond the brief?

Start with your email. I will ask what you built and which client you mean before confirming whether the £50 review is feasible. No access to your code, systems or client records.

Enquire about a Screen £50