Telemudanza: building a useful beta before automating everything
A household move starts long before the first box is sealed. A useful quote needs the route, an approximate date, access details, furniture and anything that may need storage. When that information arrives incomplete, moving companies spend time asking follow-up questions and customers receive quotes that are difficult to compare.
Telemudanza began with a simple question: can that first conversation be prepared properly without making a company travel to the property and without turning the customer into a surveyor?
The first answer was not a large platform. It was a small, assisted and testable beta.
What the first version does
The website asks only for the essentials: origin, destination, approximate date, basic home details and whether storage may be required. It then explains what happens next: a person reviews the request on the following working day and agrees with the customer how best to complete the file.
There is an important decision behind that simplicity: the public beta does not accept direct uploads of photos, videos or documents. Before collecting information about somebody’s home, a service should know what it needs, why it needs it, where it will be stored and who can see it. The first version makes that boundary visible and keeps a person between the initial form and any sensitive documentation.
Nor does it promise an instant automated quote. Its job is to create a shared starting point that reduces omissions before a moving company assesses the work.
Telemudanza does not sell packing supplies. If you need cardboard boxes, packing tape or other products for protecting and organising your belongings before the move, you can find them at TeleCajas, another project featured on this website.
The most important word on the page is “beta”
New websites often try to look more mature than the business behind them. They fill the homepage with automation, artificial intelligence, guaranteed outcomes and figures that have not yet been validated.
Telemudanza takes the opposite route. It says that the service is an assisted beta, limits its initial area and distinguishes a pilot hypothesis from a validated public price. That may look less spectacular, but it makes it possible to learn from real users without creating a false expectation.
A beta should not be a careless version. It should be the smallest version capable of completing a useful process and teaching the team something specific.
Choosing not to automate is still a product decision
On paper, this service invites automation: object recognition, volume estimates, video classification or instant quote generation. Some of those functions may make sense later. Adding them before the real workflow is understood creates cost, mistakes and privacy risk without proving that they solve the main problem.
At this stage, human review performs three jobs at once:
- it spots missing information;
- it explains what documentation is genuinely useful;
- it checks whether the prepared basis would help a company quote the move.
Technology supports that conversation rather than replacing it.
A website should explain what it does not do
The design priority was not to accumulate sections. It was to answer four questions clearly:
- What is Telemudanza useful for today?
- What does an interested person need to do?
- What happens after the request is sent?
- Which functions are not yet part of the beta?
That is why the navigation is short, the calls to action lead to one request form and moving companies have a separate route. Privacy warnings are not buried in the footer: the page explicitly asks people not to send documents or audiovisual material through the public form.
Clarity is not a layer of copy added at the end. For a new service, clarity is part of the product.
What this project teaches about launching a new website
Telemudanza offers lessons that apply to almost any early business:
- Start with the bottleneck. Here it was not the final price calculation; it was collecting enough comparable information.
- Keep the form small. Every field should justify its place in the first conversation.
- Keep a human route. While a process is still learning, a person handles exceptions better than premature automation.
- Publish the boundaries. Saying “not yet” builds more trust than dressing an aspiration up as a feature.
- Design to learn. The website should create conversations and evidence for deciding what to improve next.
A public project, not yet a success story
Telemudanza now appears in the Relógica project portfolio because the website is live, inspectable and represents a concrete way of building: controlled scope, verifiable messages and one clear next step. We are not presenting it as a commercial success or a fully validated system.
The interesting work begins now: talking to households and moving companies, observing where doubts appear and improving the process with evidence rather than assumptions.
You can visit the Spanish-language beta at telemudanza.com.