Wahlu
Social media scheduling software with a content calendar, evergreen queues, AI planning and a hosted MCP server for AI agents.
SaaS and MVP development
We build software products that people sign up for and pay for. That includes accounts and teams, subscription billing, the core workflow, the emails and the marketing site. We also run two SaaS products of our own, Wahlu and Skill Readiness, so we know what happens after launch.
Case studies
Related work
Skill Readiness
A platform for running skills assessments, with dashboards for programme owners and a report and growth plan for every participant.
What we build
SaaS & MVPs
A focused first version
The smallest version that does the main job well enough for real customers to pay for it.
Accounts, teams and roles
Sign-up, sign-in, invitations and workspaces, with the right people seeing the right things.
Billing
Stripe subscriptions, plans, credits and invoices, including upgrades, downgrades and failed payments.
APIs and integrations
A REST API, webhooks or an MCP server so other software and AI agents can use your product.
Email and notifications
Transactional email, reminders and in-app notices that arrive when they should.
Marketing site
A fast site with pricing, docs and pages written for search, built alongside the product.
Approach
How we build it
We decide early what the first paying customer needs and build that first. Features that can wait go on a list for later.
Our SaaS products are TypeScript monorepos: Next.js for the app and site, small Node services for background work, MongoDB, and Google Cloud Run so each part deploys on its own.
Questions
Common questions
Can you build an MVP?
Yes. We scope a first version that real customers can use and pay for, launch it, then improve it from what they do.
Do you handle payments and subscriptions?
Yes. We use Stripe for subscriptions, one-off payments, credits and invoices, including the edge cases such as failed payments and plan changes.
Can you work on a product that already exists?
Yes. Tell us what it is built with and what needs to change, and we will say whether we are the right team for it.
Working together
How an enquiry works
No sales calls to book. Tell us about the project and we’ll take it from there.
Send an enquiry
Tell us what you need built, what you use now and roughly when. A few sentences is enough to start.
Steve reads it
Every enquiry is read by Steve, the founder. If it looks like a good fit, he replies by email with questions.
Talk it through
If the project suits us both, we talk through what to build first and how to get there.
Building a software product?
A few sentences is enough. Steve reads every enquiry and replies by email.