the idea in your head, working in three weeks

You know the problem, from living it or from your customers. I'm Pierre. I build the first working version with you: software that runs on your real data, built around the way you already work. Three weeks, one fee, and you keep everything.

the problem

good ideas end as documents

You can describe the system you need in one conversation. Getting it built is where it stalls.

what happens

the idea stays a slide

The agency wants a brief and three months. The freelancer wants a spec you can't write. A technical partner wants half of the business. So the job stays manual, and the idea waits.

how it feels

you know the problem and can't get it built

You know the problem from your own work or your customers. You can't turn it into a system. Every month it stays in your head costs a little more.

why it matters

an idea that works should become real

A system that runs on your real data. You own it, and if it earns more, we grow it.

this is for you if
  • you live the problem daily, or you've validated it with real customers
  • you have customers, a practice, or a list of people who said yes
  • you can put a working version in front of 10 real people in the first month
  • you want to own the system, and maybe grow it
not yet if
  • nobody has asked for it yet. Find the first ten people who have; the build will wait.
  • you want to hand over a brief for someone else to execute. I build with you, in the room.
  • you need a prototype to pitch with. I build systems that run on real data, for real customers.
  • you are not sure. Take the 5-minute readiness check; it ends with a draft problem card, and I send back the finished one free.
the guide

I used to hand over decks

Years in UX, research and strategy, handing over decks that someone else was meant to build. Most never were. So I became the person who takes the idea from the first conversation to a working system. I use AI for most of the code and decide what gets built.

I'm Pierre Chalita. I run Eckwip as a small systems lab in Abu Dhabi. Some of the people I build with come from years in their field, some from a problem they validated last month.

Pierre Chalita on LinkedIn →

the plan

three steps, three weeks

No 40-page proposal. We start with the job or the idea, and finish with a system you run without me.

01

the problem card

A free 30-minute video call. You walk me through the job or the idea exactly as it is today, spreadsheets and WhatsApp threads included. You leave with a one-page problem card either way. If there is a build, the fee is agreed on that call.

02

a working version in 3 weeks

No slide deck, no mockups. In three weeks a system runs on your real data: no-code tools where they do the job, custom code where they don't. Code and accounts are yours.

03

30 days of fixes

You run it for 30 days and I fix whatever fails in real use, included in the fee. You leave with the code, the accounts and a plain note on how it works.

the deal

one build, one fee

Every build ends the same way: a working system, a plain handover, fixes after launch. The fee we agree on the first call is the fee you pay.

the build

You bring the job or the idea. I build the first working system around the way you already work.

most land betweenAED 5,000 and 15,000

one fee, fixed on the first call · half to start, half on day 30

  • one system, built end to end
  • a working version in 3 weeks
  • 30 days of fixes after handover
  • code, accounts and a plain-language note, all yours
  • no retainer, no lock-in, no second invoice
Book the free 30-minute call

Not sure it's ready? Book anyway. If an existing tool does the job, I'll say so.

what you don't risk

the guarantee

You pay half to start and half on day 30, and only if the system is part of your week by then. If it isn't, you keep that half and the code.

50% to start50% on day 30, if it stuckthe code is yours either way

the second step

some builds become long-term partnerships

The build is the whole deal. If the system works and I believe in it, I am open to staying in as a partner: a share in the business, or lifetime access to what you make. Five are running now.

  • Decided after the build, never as a condition of it. My call to ask, yours to accept.
  • Saying no changes nothing: the fix period, the handover and the code are yours either way.
  • The build fee is not credited against the share; they are two separate deals.
  • I state my hours a month in writing when we partner.
  • Nothing you show me on the call is reused. Code from your build is reused elsewhere only as generic parts.
the five

built with the people who run them

No screenshots and no numbers here: AI can fake both. The people are real, and so are the names. Ask me for an introduction.

01 · with ankit

OneFitt

Programs, bookings and check-ins for a performance and longevity coach. Now the system behind the practice.

in daily use · abu dhabi

02 · with andrew

3Dmarx

Video wayfinding for hotels and resorts. Scan a code, follow a first-person walk to where you are going.

pilot in build · dubai

03 · with ralph

LouPe

Deal flow for a commodities brokerage. Quotes, counterparties and paperwork in one place instead of an inbox.

in daily use · dubai

04 · with tarik

Tareeeq

Noura, a companion for UAE traffic. She talks you through the drive, then turns it into a short song you keep.

prototype · sharjah

05 · with mo

Kooah

Teaches 9 to 12-year-olds how their body, food and money work, on the iPad they already hold.

prototype · abu dhabi

06 · with you?

the next one

Each of these started as a build for the person who runs it. Bring the job or the idea, and we find out on the call whether a build is the right next step.

questions

what I get asked first

my data is a mess. is that a problem?

It's the normal starting point. Most builds begin with a spreadsheet export and a WhatsApp history. Sorting that out is included.

how much is a build?

Most builds land between AED 5,000 and 15,000. One fee, fixed on the first call before anything starts, half up front and half on day 30. Where it lands depends on how much has to be custom code rather than no-code tools. I say the number on the call. You can say no, and you still leave with the problem card.

will I actually stick with it?

That's what the fix period is for. I watch where it fails in real use and fix the system. If it isn't part of your week by day 30, you keep the second half of the fee and the code.

what happens when it breaks after day 30?

Message me. Faults in what I built are fixed free for 90 days after handover. New work is a new small build, priced the same way: one fee, agreed before I start. There is no retainer, and nothing expires.

do you partner with everyone?

No. Every build ends with a system you own outright. The partnership is my call to ask and yours to accept, and it comes after the build, never as a condition of it.

what happens after the fix period?

The system is yours: code, accounts, and a plain-language note on how it works. Run it without me, or come back when the next job needs a system. No lock-in either way.

why not off-the-shelf software?

If a ready-made tool fits how you work, use it, it's cheaper. I build for the jobs where the template doesn't fit, shaped around the way you already work, paid once.

contact

bring the idea

The first call is 30 minutes, free, and on video. Bring the job or the idea; you leave with a one-page problem card either way.