Rebuilding Dialessa around cold outbound calls, with solar as the example

Update, 20 October 2026: a day later I went back to speed to lead, with real estate as the main niche. The solar cold-calling homepage is gone and dialessa.com is the real-estate page again.

Today was about making Dialessa say clearly what it does: outbound cold calling. I spent 8 hours of active work in 1 long session with coding agents, typed 29 prompts, and ended up with 48 commits, 30 deploys and 47297 lines of code changed. The website, the web app and the API all went to production.

A homepage that leads with outbound

I rebuilt the homepage around cold outbound calling and used solar as the worked example. The old homepage wasn't wrong, but it was trying to cover too much, so I moved it to its own industry page instead of deleting it.

The demo form and the voices page now open on the solar example too, and the demo plays as an outbound cold call. Before this, a visitor could land on the site and hear something that didn't match what the headline promised. Now the message and the demo line up.

Simpler plans

I simplified the plans so the same set appears on every page and in onboarding. That sounds obvious, but over time small differences had crept in between the website and the app, and it's the kind of thing that quietly erodes trust. The app now describes usage in call minutes, which is how people actually think about a calling product.

I also removed the setup fee and the minimum term, so plans now run month to month.

Onboarding that does real work

Most of the day went into onboarding.

• A working rate card and FAQ upload step, with the option to skip it.
• A Your business step that reads a customer's website into a profile they can edit and confirm before saving.
• A voice step with a playable clip for each voice.

The Your business step was the most interesting to build. Reading a website gets you most of the way, but it's never perfect, so the profile has to be easy to correct. I decided the customer always confirms before anything is saved. The agent is going to speak on their behalf, so they should see and approve what it knows.

The example calls now introduce the agent as Dialessa, which makes the voice clips feel like the real product rather than a generic sample.

Outbound dialling, built together

The biggest piece of engineering was the outbound dialling system. The infrastructure scripts, the API, the worker and the voice engine were built, reviewed and merged together. Keeping them in step was the hard part. Each piece depends on the others' assumptions, and merging them separately would have left the system half-connected for a while. Reviewing them as a set took longer, but it meant the parts actually fit when they landed. It's good progress, not finished.

What was hard

The volume. 30 deploys across the website, app and API in a day means a lot of small releases, and each change in positioning touched several places at once: homepage copy, the demo, the voices page, plan listings, onboarding. Repositioning a product isn't really a copy change. It runs through everything a customer sees.

What I learned

• Pick a worked example and commit to it. Solar gave every page something concrete to point at.
• Consistency across pages matters more than I'd been giving it credit for, especially for plans.
• When parts of a system depend on each other, reviewing and merging them together is slower but less painful.
• Small, frequent releases made a day this big manageable.