I'm Ricardo, a software developer. If you're bidding for a contract and part of it needs an
application built, I can take that part on: a defined piece of software, scoped and priced with
you before the bid goes in.
You lead the bid and the relationship with the buyer. I build what we've agreed, and I'm clear
about what I can and can't provide.
Plenty of tenders combine consultancy, engineering or specialist knowledge with software
that someone has to build. If your team brings the expertise and the bid experience, I can
take responsibility for the software as a work package we've written down together: what it
does, what's out of scope and how you'll check it's done.
That could be an alpha or prototype, a register or internal tool, a summary view for
decision-makers, or a workflow that has to sit alongside the systems a buyer already uses.
Before you submit
The useful work starts before the bid goes in. Depending on the deadline and what you need, I
can:
Read the specification with you
Pick out the software requirements, the assumptions behind them and the questions worth
putting to the buyer before the clarification deadline.
Write the software plan
Set out deliverables, milestones, dependencies and what the buyer would need to provide,
then give you a price and timescale for my part.
Build a working concept
A small demonstration with made-up data, if it helps your team decide or explain the
approach. It's labelled as a concept, and we agree first who owns it and how it can be used.
What we'd settle early
Every tender is different, so these are the questions I'd want answered before either of us
commits.
The opportunity
The buyer, the procurement route, the deadlines and how the bid will be scored, and whether
you've already decided to bid.
The split
What I'm responsible for, what your team handles, where the handoffs are and who signs off
the software.
The terms
The evidence each of us provides, whether remote delivery is allowed, who owns work done
before the bid, payment if it doesn't go ahead, and support after launch.
I'm one developer, not an agency. I haven't delivered a public-sector contract yet, so I
won't claim a track record I don't have. What I can show you is software I've designed,
built and run myself.
If a tender asks for experience, certifications, insurance or capacity that I can't provide,
I'll say so when we first talk, so you can decide whether the arrangement still works for
your bid.
Software I've built
These are my own projects, not completed tender contracts.
Care Intel
Tender intelligence for UK health and social care providers. It pulls live notices from
Contracts Finder and Find a Tender, matches them to a provider's services and tracks each
bid to submission, so I've spent time inside how notices, lots and deadlines work.
A booking system built around one shared core, with Stripe deposits, reminders and an
operator dashboard. Business profiles adapt it to clinics, studios and other appointment-led
services.
Send me a link to the notice, the part of the work you'd want help with and your submission
deadline. I'll tell you plainly whether I think I can help and what I'd need to know next.