Linkdr

Sign in

We will text you a 6-digit code. No password to forget.

What it does

Swipe to hire

— Send a job with one gesture.

Real distance

— PostGIS ranks by metres, not postcodes.

Verified pros

— ID, insurance and licence checked first.

Chat per job

— Private, with photos and receipts.

Quote to booking

— Agree a price, book the slot, confirm.

Blind reviews

— Hidden until both sides have written.

Still to decide

Everything below already has a behaviour. These are the ones worth choosing deliberately rather than inheriting.

Money

Do we hold the money until the job is done, or do customers pay the pro directly?
Today: Nothing is charged. Quotes and bookings work; no payment is taken at any point.
What is the commission, and who pays it — the customer, the pro, or split?
Today: Set to 15% in config, applied nowhere.
Deposit up front, or the whole amount on completion?
Today: Neither. The slot is booked on a promise.
A customer cancels the day before — what do they owe?
Today: Free up to 24h before, then 25%. The rule is written and tested; no money moves.

Scheduling

Do pros publish real availability, or is a time agreed in the chat?
Today: Agreed in chat. The customer picks any date and time when accepting a quote.
Should the system stop a pro being double-booked?
Today: No check. Two customers can book the same pro for the same hour.
If a customer never confirms the work is finished, should it auto-confirm?
Today: It waits forever. A 72-hour rule is written but nothing runs it.

Trust and safety

Should we block phone numbers and emails in chat?
Today: Anything can be sent. Two people can agree to take the job off the platform.
What happens when the two sides disagree about finished work?
Today: A disputed state exists in the model. Nothing can reach it.
ID checks — automated, or a person reviewing documents?
Today: A person. Documents are uploaded and reviewed by hand in the admin queue.
A pro’s insurance expires. Do they come off the platform automatically?
Today: The expiry date is stored. Nothing checks it.

Launch

Launch with the trades we have supply for, or all fifty?
Today: Fifty trades listed; eight have any pros. The rest look empty to a customer.
One city, or several from the start?
Today: One. The city is a setting, so a second is configuration rather than a rebuild.
Which events are worth an SMS, given each one costs money?
Today: A pro is texted about a new job and an answer. Messages and bookings are silent.

Delivery and cost

To build and launch

$4,400–6,000

One-off. Where it lands depends on the answers above.

Timeline

6–10 weeks

Six if the open questions are settled early, ten if they are not.

Hosting, per month

Managed PostgresThe database, with PostGIS$15

Managed RedisSessions, caching, job queue$15

App PlatformRuns the app itself$24

SpacesPhotos and documents$5

Total$59/mo

You pay DigitalOcean directly. This is not part of our fee and there is no markup on it — the account is yours, so you can see the bill and change the plan without going through us.

$59 is the smallest tier of each. Enough to launch on and to run while the platform is finding its first customers.

Costs rise with use, unevenly. The database is the first thing that will need a larger plan; storage creeps up slowly as photos accumulate; the app itself can stay where it is for a long time.