Technical advice for founders and small teams
If you don't have a senior engineer yet, it can be hard to know whether a technical decision is a good one. I can give you a straight answer on architecture, scope, agency quotes or whatever else you're weighing up.
The details
Usually includes
- Architecture and technology choices
- Scoping a first version
- Reviewing agency or freelancer proposals
- Engineering practices and code review
- Light ongoing support
What you get
- A clear opinion on the decision in front of you.
- The trade-offs, written down.
- A sensible next step.
A good fit if
- You need a technical view before committing to a build or rebuild.
- You're choosing between agencies, freelancers or hiring.
- Your team is shipping, but you're not sure the foundations will hold.
How it usually goes
- Talk through what you're building, the team and the constraints.
- Work out which risks and trade-offs actually matter right now.
- Recommend a next step with sensible scope.
- Stay involved if it's useful.
Things I look out for
- MVPs trying to do too much
- Architecture that's too heavy for the stage you're at
- Agency work that nobody is checking
- Security and data decisions left too late
Questions
Can you help before we're ready to build?
Yes. That's often the most useful time, while the idea is still flexible.
Will you recommend tools and architecture?
Yes, as far as the decision needs. I usually lean towards simple, well-understood tools over whatever's newest.
Do you offer ongoing support?
Sometimes, if there's a clear reason for it. Get in touch and we can work out what makes sense.
Want to talk it through?
Book a quick call, or send me a bit of context and I'll let you know if it sounds like something I can help with.