How we work

From the first conversation to the releases after launch: what happens, in what order, and what you have in your hands at the end of each step.

See our work

Why we exist

We believe no good idea should die because of the distance between a founder’s vision and what an investor, or a first customer, can see. WeaveLines exists to close that distance: to turn an idea into something people can use, quickly enough that the founder learns from real users while there is still time to change course.

We started in 2017 and have launched 36 MVPs since. Most of what we know about launching comes from those products, and from coaching 150+ startups across 12 mentorship programs.

The process

Five steps. Each one ends with something you can use, and you always know what comes next.

  1. 01Discover

    We start with your goal, your users and whatever already exists: a deck, a prototype, a product that needs rescuing. AI-assisted research gives us a first read of the market, the competitors and the personas before our first working session, so the session itself goes to decisions.

    You leave with a first version worth building, and the reason behind every feature that did not make it in.

  2. 02Prototype

    Before anyone writes production code, you get a high-fidelity interactive prototype in days: real screens, real flows, something you can click through, show to customers and put in front of investors. It looks and behaves like the product.

    A designer directs it with Claude Design, Figma Make or Replit, validates it with you, and then designs the interface and the design system in Figma while engineers start building from the prototype.

  3. 03Build

    Engineers build from the validated prototype in the stack the product will grow in: TypeScript, the React ecosystem on the web, React Native with Expo on mobile, Node.js behind them. They use AI coding tools every day, and every change is reviewed by a second engineer before it ships.

    Automated tests and CI run on every change, and you see working software regularly, with a demo at each step.

  4. 04Launch

    Most MVPs go live 2 to 6 weeks after kickoff. Launch means the app stores or the web, with monitoring and error tracking in place before the first user arrives.

  5. 05Grow

    After launch the work changes shape: fixes, new features, the next release. We stay on a monthly retainer for support and growth, or take the fractional CTO or CPO seat when that is what you need. AI-assisted monitoring and error triage keep the small problems small.

How we work with you

Five things that hold on every project, whatever its size.

  • Decisions with you, in writing

    Scope, priorities and every cut are decided in working sessions with you and written down, with the reason next to each item.
  • Working software, regularly

    You review working software as it takes shape, with a demo at each step.
  • Reviewed, tested, monitored

    A second engineer reviews every change, automated tests and CI run before anything ships, and monitoring and error tracking are in place before the first user arrives.
  • AI where it saves time

    Research, first drafts, prototypes, coding assistants, test generation and error triage. People make every decision that matters.
  • The people doing the work

    From the first call you talk to the team that will shape, design and build the product. Faten, our founder, takes the first conversation herself.

What sets us apart

Three things clients tell us they did not find elsewhere.

  • Client-first

    Every client starts somewhere different: an idea, a prototype, a product that needs rescuing. The process adapts to where you are, and the people you talk to are the people doing the work.

  • Priced for startups

    We know what an early budget looks like. Fixed-price scopes when the work can be defined, time and materials when it cannot, and a clear recommendation on which one fits before anything starts.

  • A process that has been tested

    36 MVPs launched since 2017. The process has been run enough times to know where products get stuck, and it is built to get you real user feedback early, while there is still time to change course.

They encourage us to take the project step-by-step and consider what the user journey will look like.

Firas Aloui, Hotlas

Startups we have launched with

Some of the startups that have been through this process with us.

How we engage

Four ways to work with us. Most projects start with one and move to another as the product grows.

Fixed-price project
A prototype, an MVP or a scoped feature, delivered for an agreed price and scope.
Time and materials
Ongoing product work billed monthly by the effort spent, for work that is open-ended or changes often.
Retainer
Support, fixes and steady iteration after launch, for a fixed monthly amount.
Fractional CTO or CPO
A WeaveLines lead takes the technical or the product seat part-time: tech decisions, architecture, team mentoring and product direction, without a full-time hire.

Frequently asked questions

  • How long does it take to launch an MVP?

    Most MVPs go live in 2 to 6 weeks, and in 2 when the scope is tight. What moves the number is how many flows the first version needs, whether it ships on the web or in the app stores, and how fast decisions get made on your side. WeaveLines agrees the scope and the plan with you before work starts, and you see the product regularly as it takes shape.

  • What does the design work look like?

    A high-fidelity interactive prototype in days, generated with Claude Design, Figma Make or Replit and directed by a designer, then the interface and the design system in Figma, running alongside engineering rather than before it. Designers lead the work and review every AI output. The WeaveLines product design page lists the deliverables.

  • Where does AI come into the work, and where do people decide?

    Where it saves time without lowering the bar: research and personas in discovery, first drafts of specs and backlogs, the prototype itself, coding tools in engineering, test generation and review in QA, error triage after launch. People own the decisions at each step: what to build, what to cut, whether a change is good enough to ship. Every change is reviewed by a WeaveLines engineer before it goes live.

  • Which tools and technologies do you use?

    The TypeScript ecosystem end to end, with the stack chosen for each product, and AI coding assistants as part of how our engineers work every day. The MVP, web, mobile, desktop and AI development pages list what WeaveLines builds with in detail.

  • How do we pay?

    Four ways: a fixed price for a scoped prototype, MVP or feature; time and materials billed monthly for open-ended work; a retainer for support and growth after launch; or a fractional CTO or CPO engagement. Most clients start with a fixed-price MVP and move to a retainer or time and materials once the product is live. WeaveLines will tell you which one fits before anything starts.

  • What happens after launch?

    The product keeps changing, so the work does too. Monitoring and error tracking are in place before launch, so problems surface early. From there most clients keep WeaveLines on a monthly retainer for fixes, improvements and the next features, and some ask us to keep the CTO or CPO seat part-time.

  • Who will I be talking to?

    The people doing the work. From the first call you talk to the WeaveLines team that will shape, design and build the product, and Faten, our founder, takes the first conversation herself.

From idea to product

A process built to get real user feedback early, and a product that goes live in weeks. Thirty minutes with us and you will know what it would take.

Get in touch with us

Reach out to us to explore limitless possibilities for your startup. Let’s collaborate and transform your ideas into success stories.

Connect with us

Our offices

  • HeadquartersWeaveLines LLCrue Slah Eddine Bouchoucha2026 Sidi Bou SaidTunis, Tunisia
  • Tunis OfficeWeaveLines LLC39 rue Ibn Khaldoun1002 Tunis, Tunisia