How We Work: From Free Call to Production Software in 30 Days

Four stages. Each earns the next. No long-term contracts. Here is exactly what happens when you work with Hello Crossman.

Four stages. Each earns the next. Free call, Discovery £5K, Build £15–45K, Ongoing £250–2K/month. Here is exactly what happens at every stage when you work with Hello Crossman.

Every service business founder who contacts me asks the same question within the first five minutes: "How does this actually work?"

Fair question. You've seen the case studies. You know the timelines. But what actually happens between "I have an idea" and "550 people just signed up"? This post is the answer.

The short version

There are four stages. Each one earns the next.

Free call — we figure out if there's a real opportunity. Discovery (£5K) — we plan exactly what to build. Build (£15–45K) — we ship production-ready software in 30 days. Ongoing (£250–2K/month) — we grow what we've built.

You never commit to the next stage until the current one delivers. Discovery earns the build. The build earns the retainer. If any stage doesn't feel right, you stop. No long-term contracts. No six-figure commitments before you've seen a line of code.

Here's what each stage looks like in detail.

Stage 1: The free call — see the opportunity

This is a 30-minute conversation. Not a sales pitch — an honest assessment of whether your business has a software product hiding inside it.

I'm looking for three things: a repeatable process you run for clients (the methodology), a clear pain point that software could solve (the problem), and a business model that makes the economics work (the revenue).

Most service businesses have all three. A recruitment firm's matching process. A compliance consultancy's assessment framework. A training provider's curriculum structure. An agency's project delivery workflow. These are methodologies that run on spreadsheets, email, and manual effort — and they're exactly what becomes software.

What you get from this call: a clear yes or no on whether building makes sense, a rough sense of what the product would look like, and an honest recommendation on timing. If I think you should wait six months, I'll say that. If I think you should use an off-the-shelf tool instead of building, I'll say that too.

About half the people I talk to aren't ready to build yet. That's fine. The call costs nothing, and knowing you're not ready is more valuable than starting something premature.

Stage 2: Discovery (£5K) — plan the product

Discovery is where vague ideas become build-ready specifications. This is the most important stage, because every problem I've seen in software development traces back to building the wrong thing — not building it badly.

Week 1: Understanding your methodology

I spend the first week inside your business. Not observationally — actively mapping how you deliver value to clients. What steps does every engagement follow? Where do you make judgment calls? What data do you collect? What gets repeated across every client? What's different?

This is methodology mapping. The goal is to identify the repeatable workflows that could become software features, and the judgment calls that could become AI-powered decision support. Not everything should be automated. The art is knowing what to systematise and what to leave human.

Week 2: Specification and architecture

The second week produces the deliverables:

A build-ready specification covering every feature, user flow, data model, and edge case. This is not a traditional PRD designed to persuade a committee. It's a specification designed for AI coding tools — structured data models, explicit user flows, and precise feature definitions that Replit Agent or Cursor can execute.

A technical architecture document covering database schema, API structure, authentication approach, payment integration, and deployment strategy. This is the blueprint.

A feature priority matrix separating "must have for launch" from "nice to have for version 2." Radical scoping is the discipline of removing everything that doesn't directly generate revenue or validate the core hypothesis.

A cost estimate and timeline with enough precision that there are no surprises in the build phase.

A go/no-go recommendation. If Discovery reveals that the product doesn't have a viable market, or the complexity exceeds the budget, or the timing isn't right, I'll tell you. I'd rather save you £15–45K than build something that won't work. About 15% of Discovery sprints end with a "not yet" recommendation — and every founder who's received one has thanked me for it.

The specification document is yours regardless. If you decide to build with someone else, or build it yourself, or wait six months — the spec works with any developer, any agency, any AI tool. You've paid for the thinking, not for a dependency on me.

Read more about how Discovery works in The Discovery Sprint: How We Find the Product Inside Your Service Business.

Stage 3: Build (£15–45K) — ship production-ready software

This is where software goes from specification to production in 30 days. Not a prototype. Not an MVP that needs "phase 2." Production-ready software with authentication, payments, admin dashboards, email systems, error handling, and everything needed to launch to real users.

How the 30 days break down:

Week 1: Core platform and frontend. I build the interface first — frontend-first development. By the end of week 1, you can see the product. You can click through screens, understand the user flow, and give concrete feedback. "Move this here" is clearer than "I'm not sure about the information architecture."

This is the most important week for alignment. Every decision that's wrong at this stage is cheap to fix. Every decision that's wrong at week 4 is expensive.

Week 2: Backend and integrations. Database, API, authentication, and third-party integrations (Stripe, email, external APIs). The frontend from week 1 connects to real data. Features start working end-to-end.

Week 3: Production hardening. This is the final 10% — the work that separates prototypes from products. Security auditing, error handling, edge cases, performance optimisation, input validation, rate limiting, and deployment infrastructure. AI coding tools get you 80% of the way fast. This week is the 20% that makes it safe to put real users and real money through the system.

Week 4: Testing, polish, and launch. Client testing using TestFlow (guided testing with automatic screenshots and issue capture), final bug fixes, deployment to production, and launch support. You go live with confidence because the product has been hardened, tested, and stress-tested.

Where you land in the £15–45K range depends on complexity. A client portal with a few key workflows sits at the lower end. A two-sided marketplace with matching algorithms, document verification, and real-time messaging (like RiskPod) sits at the higher end. Discovery defines the scope precisely, so there are no surprises.

What you own: Everything. The code, the database, the deployment, the domain. I build on your infrastructure from day one. If you decide to part ways after the build, you have a complete, working product that any developer can maintain and extend.

Communication during the build: Daily async updates showing what was built, what's next, and any decisions needed. You're never wondering what's happening. You see progress every day, and you can steer it in real-time.

Stage 4: Ongoing (£250–2K/month) — grow what we built

Launch isn't the end. It's the starting line. Once real users arrive, you learn things no specification could predict. Features need adjusting. New opportunities emerge. Usage data reveals what matters and what doesn't.

The ongoing retainer covers:

Feature iteration based on real user feedback and analytics. Not roadmap items from a brainstorm — features driven by actual usage data tracked through ClearMetrics.

Bug fixes and maintenance. Production software needs ongoing attention. Dependencies update, APIs change, edge cases surface. This is the work that keeps your product reliable.

Performance monitoring and optimisation. As usage grows, what worked for 50 users might not work for 500. Proactive monitoring catches problems before users notice them.

Strategic product advice. Which features to build next. When to raise prices. How to structure upsells. When to expand into adjacent markets. This is where 18 years of product experience and 100+ builds add the most value — the judgment calls that data alone can't make.

The retainer is month-to-month. No lock-in. If the product is stable and you don't need ongoing development, you scale down or stop. RiskPod started at £10K/month ongoing development because the platform is actively growing. Simpler products might need £250/month for monitoring and occasional updates.

What makes this different from agencies

Traditional agencies work like this: you brief them, they disappear for six weeks, they come back with something that doesn't match what you imagined, you iterate for three months, you eventually ship something acceptable at 2x the original quote.

The problem is structural. Agencies staff projects with specialists: product strategist, designer, frontend developer, backend developer, QA, project manager. Five or six people, all coordinating with each other and with you. Every handoff adds delay. Every meeting takes six calendars to schedule. Every miscommunication between designer and developer costs a sprint.

I work differently because the model is different. One person making product decisions, design decisions, and implementation decisions simultaneously. No handoffs. No coordination tax. No waiting for the next sprint review.

This doesn't mean I'm doing everything alone — AI coding tools handle the repetitive work. Replit Agent generates code. BuildKits generates specifications. But the decisions — what to build, how it should work, what the user experience should feel like — those come from 18 years of doing this across 100+ products for brands like Google, Microsoft, Disney, and Samsung.

The result: 30 days instead of 6 months. £15–45K instead of £50–150K. Same quality. Dramatically less overhead.

Who this is for (and who it isn't)

This works best for: Service business owners (agencies, consultancies, recruitment firms, training providers) who have a proven methodology, existing revenue, and a clear pain point that software could solve. You're cash-rich but asset-poor. You're at capacity. You're watching competitors ship products. You know there's a SaaS hiding in your business — you just don't know how to get it out.

This also works for: Creators with 5K+ engaged followers and a structured methodology. Through joint ventures, creators contribute distribution while I contribute build capability. No upfront cost. Revenue shared. FounderOS hit £8K MRR in month one using this model.

This isn't for: Bedroom entrepreneurs with app ideas and no existing business. Mobile apps. Blockchain projects. Businesses without a proven methodology or existing client base. If you're pre-revenue and pre-methodology, you need to validate the business before building software.

The bottom line

Every stage earns the next. You never commit to more than one stage at a time. Discovery earns the build by proving there's a viable product. The build earns the retainer by shipping something worth growing. If any stage doesn't deliver, you stop.

Five case studies. Five different industries. The same process: free call → Discovery → build → ongoing. The outcomes speak for themselves: 550 signups in 48 hours. £8K MRR in month one. Automated payment recovery. Vertical SaaS in 30 days. A Canny alternative in 40 days.

---

Frequently asked questions

How much does it cost in total?

Discovery is £5K. The build ranges from £15–45K depending on complexity. Ongoing support is £250–2K/month. A typical full engagement from Discovery through launch costs £20–50K — compared to £50–150K+ from traditional agencies for the same scope.

What if Discovery reveals the product won't work?

You get the specification document and an honest recommendation. About 15% of Discovery sprints end with "not yet." The £5K bought you clarity and saved you £15–45K on a build that would have struggled.

Do I own the code?

Yes. Everything — code, database, deployment, domain. Built on your infrastructure from day one. If you part ways, you have a complete product any developer can maintain.

How do you build so fast?

Frontend-first development with AI-accelerated coding tools. One person making all decisions eliminates the coordination tax of multi-person agency teams. AI handles repetitive code generation. Human judgment handles architecture, security, and product decisions.

What if I need changes after launch?

That's what the ongoing retainer covers. Month-to-month, no lock-in. Feature iteration, bug fixes, performance monitoring, and strategic product advice.

---