PortfolioHome renovation
Home renovation software for plans, bids, and project workflow
Dwello · SaaS · Home renovation
The Dwello team defined a home renovation product for dwellopro.com. We built the live web application from scratch: the screens homeowners and contractors use, secure accounts, and the hosting and release path that keeps it running in production.
- Product design
- Web application
- Accounts and access
- Hosted application
- Releases and monitoring
01 · Story
The story
Dwello at dwellopro.com helps people manage a home renovation in one place. Homeowners and their teams can work from plans and drawings, compare contractor bids, and follow the project without juggling spreadsheets and email threads.
The Dwello team arrived with a clear product specification and no existing software. The first release had to include user accounts, a database for project data, and a path to production, because the interface is not a mockup. It talks to the live application from day one.
We built the product as a web application with a dedicated API layer and an auth gateway in front of the services that need it. Production runs on a right-sized host in AWS while the product is still evolving. Images ship from a private registry, credentials stay in a managed secrets store, and database updates run when the application starts. Tracing and host alarms give the team visibility when something breaks.
The same program includes a larger hosting layout for a later stage, so growth does not require a rewrite. For now, dwellopro.com is the application the Dwello team specified, with sign-in, permissions, and monitoring already part of the running system.
02 · Constraints
Challenges
- 01
The product was specified before any code existed
The Dwello team had already decided what the product had to do. The first build had to cover identity, data, and production hosting together, because visitors use the real application, not a prototype.
- 02
Sign-in and the product had to ship together
Accounts, permissions, and the renovation workflow belong in the same release. The auth gateway, the API layer, and the data services deploy as one unit, with secrets kept out of the codebase.
- 03
Hosting had to match an early product, not a hypothetical scale
A single production host is the right fit while the product is still taking shape. The team also has a staged path to a larger cluster when traffic and release cadence outgrow the first host.
03 · Delivery
What we did
- Translated the Dwello requirements into product rules in the API layer so the same logic serves the web app, background work, and automated checks.
- Designed and built the web interface, with generated types so the screens stay aligned with the API as both sides change.
- Built sign-in, authorization, and an auth gateway into the first production release.
- Packaged the application as containers, deployed to AWS, and kept credentials in a managed secrets store.
- Added tracing and host alarms so production issues surface with enough context to fix them.
- Prepared a larger hosting layout in the same infrastructure program for when the product outgrows the first host.
04 · Results
Outcomes
- dwellopro.com runs the home renovation product the Dwello team specified, with accounts and the interface on the same deployment.
- Sign-in, permissions, secrets handling, and monitoring are part of the live system, not a later phase.
- The team can grow hosting when the product needs it without starting the platform work from zero.
Stack
Next
Planning a site like this?
If you want a site that fits your industry and can grow without a rewrite in a year, tell us what the business needs to do online. We will respond with a clear first version and what should wait.