How did you land your first projects as a solo engineer/consultant?

I’ve spent roughly the last decade and some change as a software engineer, and recently decided to start a solo consultancy.I’m focused on helping SMEs sort out the messy back-office parts of the business: spreadsheet glue, brittle internal workflows, poor reporting, awkward integrations, backend/platform problems, and AI workflows that need to do real work rather than just look good in a demo.I’m not really interested in becoming a generic agency. I’d rather work with businesses that already feel operational pain and need someone technical to help untangle it properly.For those of you who’ve made this jump:* how did you get your first real project? * what kind of outreach actually worked? * did your first few clients come from network, content, cold outreach, partnerships, subcontracting, or somewhere else?Also, if anyone knows SMEs or operators dealing with this sort of mess, I’d be glad to chat.As a gesture of goodwill, I’m offering the first 5 clients 10 hours free to help get an initial project moving.You can find me over at https://crescita.cc

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

medium confidence

Competition

No competitor data yet

Trend

No signal yet

A solo consultant offering technical cleanup for SMB back-office operations, testing market fit through direct outreach and free trial hours.

The pain

SMEs have accumulated technical debt in their operations: spreadsheet dependencies, broken integrations, manual workflows, and reporting gaps that drain time and create errors. They know something is wrong but lack the technical expertise to fix it themselves.

The gap

Most agencies are generalist and expensive. Most freelancers are junior or unreliable. There's no trusted intermediary who understands both the messy reality of SMB operations and has the depth to actually solve backend/integration problems without over-engineering.

Build angle

This isn't a product, it's a service business testing whether the founder can acquire customers and deliver value. The real question isn't whether to build, but whether the founder can close deals and retain clients. The free 10-hour offer is a customer acquisition tactic, not a business model.

Strengths

  • Founder has 10+ years of engineering credibility, reducing trust barriers with technical buyers
  • Specific problem definition (back-office, integrations, workflows) beats generic 'software consulting'
  • SMEs with operational pain are motivated buyers who will pay for solutions that work
  • Low overhead as solo operator means better margins than agencies
  • Posting on HN shows founder understands where technical SME operators congregate

Risks

  • Service businesses don't scale without hiring, which changes unit economics and founder involvement
  • No evidence of customer acquisition ability yet, HN post is asking for advice, not reporting results
  • SMEs are fragmented and hard to reach systematically; founder may struggle with repeatable sales process
  • Scope creep is endemic in back-office projects; unclear if founder has pricing/scoping discipline
  • Free 10-hour offer signals desperation and trains customers to expect discounts; may attract price-sensitive clients who won't pay later
  • Categorized as 'Tool' and 'AI' but is actually a services business, misalignment suggests unclear positioning

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “How did you land your first projects as a solo engineer/consultant?”.

Open FlyBot