No customer project, named or not
Not a blurred screenshot, not "client name withheld", not a redraw. If it is not published with the customer's permission, it is not on this page.
Portfolio · development
No customer software on this page yet.
A development portfolio is a list of things built for other businesses. We have none we are able to name, and describing somebody else's work, or a mockup, as if it were ours is the one thing this page exists to avoid.
So instead of a list, it says what a build with us leaves you holding, and what would have to be true before a project appears here.
Everything below is something you can hold us to in writing, before anything is built.
How to read this page
01
02
03
Three things to hold in mind before the list.
Otherwise a list of deliverables reads as a list of projects, and it is not one.
Written in the offer tense
Everything below is what we would build and hand over, not a description of a job already delivered. The day that changes, the tense changes with it.
Checkable before you pay
The scope, the plan and the price are written down before any code. That document is what you can test us against, and it is yours either way.
No screenshots on this page, on purpose. An image of a screen proves that somebody can make an image of a screen.
What a build leaves you with
Six things you keep, whoever writes the code.
The software is the obvious one. The other five are what decide whether you can live with it in two years.
The scope document
What it does, who uses it, what it deliberately will not do, roughly how long it takes and what it costs. Yours whether or not we build it, and you can take it to somebody else.
The source code
Anything written specifically for your business is yours from the first day, handed over rather than held hostage.
The accounts and the database
Hosting, accounts and data in your name where that is possible. You can export it, and if you leave you take it with you.
The documentation
Written as it is built, so somebody else could pick it up without ringing us.
The checks it passed
Driven in a real browser before you see it, with every change recorded and reversible. Tested, not hoped.
Somebody watching it
Software breaks when the tools around it change. Watching it, fixing it and changing it as the business changes is quoted with the build, charged monthly, and you can stop it.
Which parts are yours and which are licensed is written down in the plan before you agree to anything, not decided afterwards.
The conditions
What has to be true before a project appears here.
Written down so it is a rule rather than an intention, and so you can hold us to it later.
Before anything goes on this page
- A real, finished piece of software for a real business, delivered and running — not a pitch, not a prototype, not a favour half done.
- That business's permission in writing to be shown, with their name on it.
- A description of what it does that the customer would agree with if they read it out loud.
What will not appear here, ever
- "Client name withheld", a blurred screenshot, or a redraw of somebody else's product.
- A mockup of something we have not built for anyone.
- A number, a percentage or a saving attached to any of it, unless the customer published it themselves.
The way this page fills is one small piece of work, done properly, with a customer willing to be named afterwards. Until then it stays exactly as honest as it is now.
Check it yourself
Four ways to check us before you commit.
None of them needs you to take our word for anything.
- OneAsk for the plan in writing
What it would do, what it would not do, how long and what it costs, on paper. It is free, and it is yours whether or not you go ahead.
- TwoRead what it will not do
The exclusions are the part of a scope worth reading twice. If they are vague, ask for them to be written down before you agree to anything.
- ThreeAsk who does the work
Some of a build is ours and some is delivered by people we work with. Ask which, for your job, and you will get a straight answer before you commit to anything.
- FourStart with one piece
Do not commission the whole thing at once. Pick the piece that costs you most, judge how it went, and decide on the next one after.
If any of those four does not go the way this page says it will, that is a defect and we want to hear about it — support@affordableleadsgeneration.ca.
Start here
Start with one piece, and judge us on it.
Half an hour on the phone, then a written plan of what we would build first. Both are free, and the plan is yours whether or not you go ahead.
Booking opens an email to support@affordableleadsgeneration.ca — send a time that suits you and we will confirm it.