Freelancyfy

Freelancyfy is an entrepreneurial project I lead as co-founder. It starts from an observation about the day-to-day of freelancers and small agencies: the “admin” side of their business is spread across many tools that don't talk to each other.

Keeping track of clients, projects, quotes, invoicing and documents often means juggling spreadsheets, invoicing tools, messaging apps and shared folders. Each tool does its job, but together they create friction:

• –the same information gets entered several times;
• –an overall view of the business is hard to get;
• –time spent administering the work is time not spent doing it.

• –A small founding team: every feature has to justify the time it costs.
• –An audience that cares about price and simplicity: the tool must be simpler than what it replaces.
• –A product that replaces existing tools has to be reliable from day one on what it covers.

• –Product vision and positioning.
• –MVP development and technical decisions.
• –Web application architecture and development.
• –User needs, UX journeys and feature prioritisation.
• –Business model thinking.
• –Coordination with co-founders and collaborators.
• –Planning the beta, user acquisition and go-to-market.

I treat Freelancyfy as both a product and a business. On the product side, I start from a freelancer's concrete journeys — finding a client, scoping an engagement, delivering it, getting paid — rather than from a feature list.

On the business side, the business model and early user acquisition are worked out alongside the MVP, not after it.

The trade-offs that shape the project:

• –MVP scope: cover the essential journeys first rather than aim for completeness.
• –Positioning: one unified workspace for freelancers and small agencies, rather than yet another single-task tool.
• –Architecture: foundations that can take new modules without a rewrite.
• –Sequencing: validate the value with a beta before broadening the product.

I take part in building the web application and in the MVP's architecture choices: application structure, data model, module boundaries. The aim is a foundation that is easy to evolve at the pace of a small team.

Freelancyfy is where I practise the whole chain: understanding a user, framing a value proposition, deciding what gets built and preparing to go to market. It is the same approach I use at work — with ownership of the outcome on top.

• –An MVP is first a decision about what not to build.
• –Technical choices are business choices too: they set the cost and speed of everything that follows.
• –A good product idea is no substitute for talking to users.