Software architecture and technical consulting
Software architecture consulting for businesses deciding how to build, or wondering whether what they have will hold: which stack to use, how to structure a system, or what is wrong with an existing one.
We work on medium-complexity business software: web applications, portals and integrations. You receive a written outcome, with the reasoning behind each recommendation and the risks in the order to fix them, and we walk your team through it. Where the honest answer is to keep what you have, we say so.
For example: a written review of an application someone else built, with its risks listed in the order to fix them.
An illustration of the kind of work we do, not a client project.
What you have
BeforeWritten review
AfterEach risk with the reason and the fix, walked through with your team.
What technical consulting includes
- IncludedCustomer sign-in, order statusNot includedMobile appDone whenTested with your real orders
Goals, constraints and current systems
We start with what the software must do, your budget, your team and what already exists.
- InterfaceWeb app for customers and staffLogic and APIsRecommended: one API for bothDataOne database, daily backups
Stack and hosting recommendations
A recommended stack and hosting set-up, with the reasons and the alternatives we ruled out.
- How a request moves todayRequestCheckApproveDoneOwner: SalesOwner: Finance
System design
The components, the data and how they connect, drawn and written so a developer can build from it.
- 1Backups never restoredFix first2Shared admin loginFix next3No monitoringPlan
A review of an existing system
Risks and fixes in priority order, from security and backups to code quality and hosting.
- Walkthrough with your team1Findings, in priority order2Your questions answered3Next steps agreedAgreed
A walkthrough with your team
A session to go through the findings, answer questions and agree the next steps.
Want this for your business?
Tell us what you need. A founder reads every enquiry and replies with questions or a proposed scope.
Not sure yet? Start with a free 30-minute call
Talk it through with a founder first. No obligation.
Who it’s for
Founders choosing a stack for a new product
A choice that suits your budget, your hiring plans and what the product must do.
Teams planning a rebuild or a major feature
An outside view before you commit months of work to one approach.
Businesses with software someone else built
An independent review of what you have, before you invest more in it.
What you receive
Everything is handed over in your name, so you can run it, change it or move it to another team.
- A written report with each recommendation and its reasoning
- A system diagram, for new builds
- For reviews: risks ranked by priority, each with a suggested fix
- Notes from the walkthrough session and the agreed next steps
What we need from you
A project moves fastest when these are ready. We help you put together anything you do not have yet.
- 1Your goals for the software, and the constraints: budget, deadline, team
- 2For a review: read access to the code, hosting and any documentation
- 3Time with the person who knows the current system best
- 4A decision-maker at the walkthrough
How an engagement runs
- Scope document
Scope: customer portal
What we deliver
- Customer sign-in, with roles
- Order status page
- Invoice downloads
Not includedMobile appDone whenTested with your real ordersAgreed by you before the build starts
- This week’s buildReady to view
This week’s increment
Order status page
feat: order status page
test: status for each order type
docs: how statuses are calculated
Next increment: invoice downloads
- Review checkpointOur reviewer
- Checked against the scope
- Tests read and run
- Ready for you
Your approval
Approve milestoneRequest changes - Handover pack
Code repository
In your account
Credentials record
Transferred to you
Documentation
What was built and how
Runbook
Deploy, roll back, fix common problems
Maintenance available on a monthly plan
Offered as
Scope: customer portal
What we deliver
- Customer sign-in, with roles
- Order status page
- Invoice downloads
Agreed by you before the build starts
What affects the cost
We quote after a scoping conversation, so there is no fixed price on the site. These are the factors that move the cost of this work up or down; the proposal states the scope, what is not included and the price.
Technologies we commonly use
- Python
- React and TypeScript
- Document and relational databases
- Cloud hosting
- REST APIs
- Payment and messaging integrations
- Size of the system
- The number of components, integrations and users involved.
- Depth of the review
- A high-level assessment, or a line-by-line look at code and infrastructure.
- Documentation available
- Systems without documentation take longer to understand.
- Number of options compared
- Comparing three stacks in depth takes longer than confirming one.
Questions
Medium complexity: business applications, portals and integrations. Work that needs specialist certifications or mission-critical uptime is outside our range for now.
A written outcome: the recommendation or review, the reasoning behind it and the next steps, followed by a session to walk your team through it.
Yes. We need read access to the code and hosting. The review states what we found and why it matters, without assuming the previous team was wrong.
We can, but you are not obliged to. The written outcome is yours to use with any team.
Only the ones you agree to in writing. Your code and data stay in the places agreed for the engagement.
Related services
Web applications and MVPs
Customer-facing apps, dashboards, portals with login and roles, and startup MVPs.
Maintenance and support
Updates, fixes, backups, monitoring and small changes on a monthly plan.
AI and GTM strategy, research and SOPs
AI adoption and go-to-market strategy, market research and process documentation.
Tell us what you want to build.
Describe the work. We will scope it with you, or tell you plainly if it is not work we should take on.