It is ours, not a client's
We are the customer for everything below. That makes it weaker evidence than a delivered project and stronger evidence than a mockup, and both halves of that sentence are worth saying.
Portfolio · development
The software we have actually written.
Every piece named on this page we built for ourselves and now run. None of it was built for a customer we can name, and describing it as if it were is the one thing this page exists to avoid.
It is here because it is the honest version of a portfolio: not a picture of work, but a working thing you can ring, at a standard you can hold us to.
Every claim below can be checked from the outside. The quickest one is (902) 707-6527 — ring it and see whether the description matches.
How to read this page
01
02
03
Three things to hold in mind before the list.
Otherwise a list of software reads as a list of projects, and it is not one.
It runs, and it is answering now
This is not a prototype in a folder. It answers a live phone line, takes real bookings and writes them into real calendars, and it did that today.
You can test it without us
The point of describing it this concretely is that each line is falsifiable. Ring the number, ask it something it should not know, and see whether it takes a message rather than guessing.
No screenshots on this page, on purpose. An image of a screen proves that somebody can make an image of a screen. A number that rings proves the thing behind it exists.
What we have written
Six pieces, and they all talk to each other.
Which is the harder half. Any one of these on its own is a weekend; the joins between them are the work.
The voice agent
Answers a live phone line day, night and weekend, in the caller's language. Asks the questions the business would have asked, and takes a message rather than inventing an answer it does not have.
The booking engine
Reads real availability rather than offering slots and apologising later, writes the appointment into Google Calendar immediately, and carries the same appointment into Apple Calendar and Outlook by subscribed feed.
The messaging layer
Sends the confirmation, then a reminder the evening before. Honours an opt-out, and gets the compliance footer right in each language it sends in.
The lead dashboard
Every call and chat with a transcript, a stage, search across the lot, export, more than one line, and access for the people who need it. It is where the business actually lives afterwards.
The setup wizard
Reads a business's own listing and its website and configures an agent from them, so the first version is close before anybody edits a word. It exists and it works. It is not linked from this tree, because this tree sells nothing.
The operator console
The screen we run the service from: lines, numbers, what each account is using, and what went wrong on a call. Unglamorous, and the reason problems get found before a customer reports them.
The website chatbot is the same brain typing instead of talking — the same services, the same hours, the same lead list. Building it twice would have been the easier and worse decision.
Be precise about it
What this proves, and what it does not.
A list of our own software is evidence of some things and not of others. Both halves belong on the page, or the first half is worth less.
What it is fair to conclude
- We can build something that runs unattended, in production, and keep it running.
- We can make real-time voice, a calendar, a messaging provider and a database agree with each other, which is where most of this kind of work fails.
- We ship the boring parts — the opt-out, the transcript, the export, the console for fixing things — and not only the demo.
What it does not prove
- That we have delivered a project for another business to a deadline and a fixed price. We have not published one, and no wording here makes that untrue.
- That we are the right shop for something far outside this shape of problem. Ask on the call and expect a straight answer, including no.
- That anything here matches your business yet. It was built for ours.
The way that gap closes is one small piece of work, done properly, with a customer willing to be named afterwards. Until then this page stays exactly as honest as it is now.
Check it yourself
Four ways to test every line above.
None of them needs a meeting, and the first one takes two minutes.
- OneRing it
(902) 707-6527. Ask for something the business would not offer and see whether it takes a message instead of guessing. That is the behaviour described above.
- TwoBook something on the call
Ask it for a time. Watch whether a confirmation arrives, and whether it is a time that was actually free.
- ThreeAsk to be shown the dashboard
On the call, ask to see where that conversation ended up — the transcript, the stage, the export. It is a screen share, not a slide.
- FourAsk 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.
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
Ring it first. Then book the call.
Two minutes on the line tells you more than this page does. After that, half an hour on the phone and a written plan of what we would build first. Both are free.
Booking opens an email to support@affordableleadsgeneration.ca — send a time that suits you and we will confirm it.