The opening claim
A client looks at my age before he looks at my architecture. He does the arithmetic, decides I was in a lecture hall eighteen months ago, and quietly moves me to the pile of people who might disappear halfway through his project.
He is not being unfair. He is being rational. He cannot inspect my code, he cannot audit my judgement, and he has been burned before by somebody cheap who vanished. Age is the cheapest signal he has, so he uses it.
You cannot argue your way out of that. I have tried. The meeting where you explain how serious you are is the meeting you already lost. The only thing that moves a sceptical buyer is software he can watch running.
The mechanism 🧠
There is a name for what is happening in that room: information asymmetry. The buyer cannot tell a good unknown from a bad unknown, so he prices every unknown as if it were bad. Economists call it a market for lemons, and it is why unproven sellers get rejected at rates their actual quality does not deserve.
The best study on this is Amanda Pallais, writing in the American Economic Review in 2014. She hired 952 freelancers with no ratings, gave them identical work, then published detailed public evaluations for a randomly chosen subset. Same workers, same skills, same platform. The only variable was whether a verifiable public record existed.
The workers who got that public record were hired at close to three times the rate of the ones who did not, moving from roughly 12 percent to roughly 30 percent. Here is the part that matters more: the same treatment did almost nothing for firms that already had a reputation. Proof is worth the most precisely when you have none.
Read that again as an operator. Publishing evidence is not vanity. It is the single highest leverage act available to somebody with no track record, and its value decays as you become established. You have a window where this works better for you than it ever will again.
Age is not the real objection. Risk is. Age is just the proxy your buyer reaches for when he has nothing else to grab. Hand him something else to grab.
Comparative Breakdown
| Signal | The proposal route | The running software route |
|---|---|---|
| What the client receives | A PDF describing intent | A URL he can open on his phone |
| Verification cost for him | High. He must trust your words | Near zero. He clicks and sees |
| What age implies | Inexperience, delivery risk | Irrelevant. The thing is already running |
| Failure mode | "Send me your references" | "Can it handle my catalogue?" |
| Who carries the risk | The client, so he says no | You, because you already built it |
| Time to trust | Weeks of meetings | About ninety seconds |
| Cost to you | A day of writing | A weekend of building |
The right column costs more up front. That is the entire point. Effort you spend before payment is the only credible signal, because a person planning to disappear would never spend it.
The Algerian reality
Here the youth penalty stacks on top of a trust deficit that was already severe.
An Algerian business owner has usually been burned by software before. Someone took an advance, delivered a broken site, and stopped answering the phone. He has no realistic legal recourse for a 200,000 DZD contract. Chasing it through a court costs more in time than the money is worth, so he simply eats the loss and resolves to never do it again. You are meeting a man who has already paid tuition on this lesson.
This is the same instinct that produced cash on delivery. Nobody here pays before they hold the product, and software is a product they cannot hold. So the buyer defaults to the physical version of the same protection: he wants to see it working, in front of him, before money moves.
Understand what that means. In a high trust market you can sell a roadmap. Here you sell a demo. A ten page cahier des charges signals effort in Paris. In Algiers it signals that you are good at documents, which is not the thing he is worried about.
What actually closes deals for me is unglamorous. A screen recording of a live dashboard with real data moving through it. A staging link he can open on his own phone, in Arabic, right to left, on the mid range Android he actually owns. A short clip of an order going from a customer tapping buy to a delivery label printing. Twenty seconds of that outperforms every proposal I have written.
The other local factor is that the market is small and talks. Algiers software is a village. One delivered project that the owner brags about in his own circle is worth more than any advertising, and one abandoned project follows you for years. Your public record is being written whether you publish it or not.
What to actually do 🛠️
Build the thing before the meeting. Not the whole product. The one flow that carries the client's fear. If he sells online, build a checkout that takes a real order end to end. Walk in with it already deployed.
Make it inspectable, not describable. A link beats a slide. Deploy to a real URL, on a real domain, with real data that looks like his business. Load it on a phone, not a laptop, because that is where his customers live.
Publish the work continuously. Ship the artifact publicly: the live site, the repository, the write up of what broke and how you fixed it. Pallais is telling you that this compounds hardest right now, while you are unknown. Every month you delay is leverage you never get back.
Show the failure handling, not the happy path. Anyone can demo a successful order. Show what happens when the network drops mid checkout, when stock hits zero, when a duplicate order arrives. Showing that you thought about failure is the fastest way to stop looking twenty two.
Let the work carry your age. Do not open with an apology or a justification. Do not raise it at all. If he raises it, answer with the URL. "Here is a system doing this in production right now" ends that conversation faster than any credential.
Charge properly. Discounting to compensate for youth confirms his suspicion that you are a student project. Price the work, then over deliver on the proof.
TL;DR 🧾
Trust equals visible proof divided by claimed intent. Your age only wins the argument when you let the argument happen. Ship something he can open on his phone, and the conversation stops being about how old you are and starts being about whether it handles his catalogue.
LINKEDIN VERSION
A client looks at my age before he looks at my architecture. He assumes I will disappear halfway through. He is not being unfair, he is being rational: he cannot inspect my judgement, so he uses the cheapest signal available.
You cannot argue your way out of that. The meeting where you explain how serious you are is the meeting you already lost.
There is good evidence for this. Amanda Pallais, American Economic Review, 2014: she hired 952 freelancers with no ratings, gave them identical work, then published detailed public evaluations for a random subset. Those workers were hired at close to three times the rate, moving from roughly 12 percent to roughly 30 percent. The same treatment did almost nothing for firms that already had a reputation.
Proof is worth the most exactly when you have none. That window closes as you become established.
In Algeria this matters more, not less. Most owners have already been burned by someone who took an advance and stopped answering. They cannot realistically chase 200,000 DZD through a court, so they protect themselves the same way they protect themselves from a bad delivery: they want to see it before they pay.
So I stopped sending proposals. I send a staging link, in Arabic, on a mid range Android, with an order going through end to end.
Twenty seconds of running software beats ten pages of intent.