Work
Three systems, all live on the internet. Open any of them and try to break it.
01 Intake agent
It answers at 2am, knows which towns you cover, and books the job. When it cannot help, it says so in plain words and hands over your number. Every decision it makes lands in a log you can read.
- The problem
- A call comes in at 10pm and goes to voicemail. The customer dials the next company on the list. You never find out it happened.
- What it does
- It holds a real conversation with whoever lands on the page, works out what they need and where they are, offers the slots that are genuinely free, and books one. Ask it about a town you do not cover or a job you do not do, and it will tell you plainly and hand over your phone number. Every decision it makes is written to a log the owner can read.
- Built on
- Server-rendered pages. A tool-using model kept inside a strict state machine. Per-business configuration for services, hours, coverage area and contact details. Conversations are bound to one business and purged the moment they reach an outcome.
- What a build like this takes
- A build like this is a $3,000 to $5,000 project depending on how many systems it has to book into.
02 Source-check
Paste a source document and a draft. Every checkable claim comes back with a verdict and a link to the sentence it was judged against.
- The problem
- Someone writes a summary of a long document. Two of the numbers are wrong. Finding out which two means reading both side by side for an hour.
- What it does
- It pulls every checkable claim out of the draft and matches each one against the source, marking it supported, missing, contradicted, or recomputed where the arithmetic can be redone. You get a permanent URL to send back to whoever wrote it.
- Built on
- Extraction and judgement run as separate stages, so every verdict traces back to a specific source sentence. Numeric matching handles units and years. A measurement harness runs the whole corpus a hundred times over to see what actually holds.
- What a build like this takes
- This one is a product of my own, so it carries no project price. It is here to show what the verification work looks like up close.
03 Lead-flow demo
Submit the form with made-up details and watch the chain fire. The lead is recorded, the owner is alerted, and if nobody touches it in 24 hours the system chases it. Every step is timestamped in a public log.
- The problem
- An enquiry comes through the website form into an inbox nobody is watching. Two days later the customer has booked someone else.
- What it does
- The submission creates a record, alerts the owner straight away, and starts a clock. If nobody has touched the lead in 24 hours, the system follows up by itself. Every step writes a timestamped line to a log that is open to the public, so you can check it fired without taking my word for it.
- Built on
- Webhook-triggered workflow. Structured lead store. Transactional email and SMS with proper consent handling. Scheduled follow-up. Demo submissions purge themselves within 24 hours.
- What a build like this takes
- A build like this is typically a $1,500 to $3,000 project.
Yours would look nothing like these.
They are here so you can see how I work: what gets logged, what the system does when it has no answer, and how much of it you are allowed to look inside. Yours would start from your workflow and go from there.