Reframe the offer
Lead with a simple promise and a clear audience instead of a sprawling list of services.
Tanta Holdings / Website Builds
First published case study for the website-builds offer.
I picked Swell Realty as the public-facing case study and kept the internal project name, BB-Moonbow, in the background. That gives the page a clean brand story, a live reference, and a concrete example of how a Tanta Holdings website build goes from scope to launch.
Social proof needs to be specific, not abstract.
The first case study should do more than say “we build good websites.” It should show the problem, show the structure, show the result, and give a buyer enough evidence to make the next decision faster.
The brief
The project had to balance branding, clarity, and the practical reality of how people scan a page.
Client problem
Swell Realty needed a site that did not feel like a placeholder. The page had to do three things at once: establish trust quickly, guide a visitor to the right next step, and keep the structure simple enough that the offer stayed clear on mobile and desktop. The site needed to read like a real business, not a template.
Build principle
“The page should make the project easier to approve, not harder to understand.”
Internal project brief
Buyers do not buy “website design” in the abstract. They buy confidence that the right message will show up in the right place, that the site will feel credible on first contact, and that the build will not become a maintenance headache the moment it goes live. The Swell Realty project gave us a clean example of what that looks like when the work is done with restraint.
Internally, the project was called BB-Moonbow. Publicly, the better story is the client name and the client result. That decision matters because case studies are not only technical records. They are trust documents. The audience is a prospect who needs to understand how a Tanta Holdings website build behaves under real use, not a developer who wants the internal nickname.
This page exists to turn that judgment into a reusable format. It gives future buyers a model they can compare against their own situation, and it gives the pricing page a concrete proof point instead of a generic promise. That is the difference between marketing copy and evidence.
A prospect does not arrive wanting to admire design decisions. They arrive wanting to know if they are in the right place. For a real estate business, that means the tone has to feel stable and trustworthy, the imagery has to feel intentional, and the call to action has to be easy to understand even if the visitor only glances at the page once. That is why the hero section had to be concise. The supporting sections add proof, show process, and create confidence that the business is real and ready.
The deliverable is not a pile of screenshots or a pretty composition. It is a sales asset. The site has to move a visitor toward action without requiring a sales call to explain what the page should have been doing in the first place. The case study is written from that perspective: not to show off the developer’s taste, but to show the buyer the shape of the deliverable and the logic behind the choices.
One hidden advantage of using Swell Realty as the first public example is that the project sits at the intersection of trust and conversion. Real estate businesses have to earn confidence quickly, but they also have to move people to a next step without burying the offer under too many paths. That tension is familiar across service businesses, so the lessons travel well.
Approach
Built to reduce friction at every decision point.
This was not a decorative redesign. The build was organized around decision-making: what the visitor sees first, what proof they get next, and how they move to the right next action.
Structure the proof
Use sections like services, property journal, and client stories to demonstrate substance without overloading the first screen.
Make the CTA obvious
Preserve the questionnaire for intake, but keep the homepage and contact route focused on the next real step.
Verify the handoff
Wire the form, test the routes, and confirm the build passes cleanly before calling it finished.
“The randomness of early-stage building has been replaced with something more reliable.”
Build log
The page now behaves like a sales asset instead of a draft. A visitor can understand the offer, inspect proof, and move toward contact without needing a separate explanation call first. That is the point of the first case study: to show the system as it works, not as a promise.
What was built
A conversion-first real estate site with a clear information hierarchy.
The finished page is structured to move a visitor from brand recognition to trust to action without making them hunt for the next step.
Site structure
- Home page with a strong hero, navigation, service story, property journal, client stories, process, coverage map, and contact form.
- Questionnaire route preserved separately so the main homepage could stay focused on conversion rather than intake complexity.
- Contact route wired through the same lead-handling pattern used across the site, so inquiries have an obvious path instead of landing in a dead end.
- A footer and header system that keeps the site feeling unified from the first view to the final CTA.
Build record
- 13 documented implementation steps.
- 2 API routes: contact handling and submission handling.
- One homepage organized into 8 visible sections, each with a distinct job.
- Zero TypeScript errors at build time.
Results
What the launch actually accomplished.
- The homepage is now organized around trust, process, and action instead of a single generic hero.
- The questionnaire lives on its own route, which keeps the main experience cleaner for first-time visitors.
- The contact route has a visible path and a functional form rather than a dead-end CTA.
What the client received
A homepage that feels deliberate, a routing system that keeps the main story uncluttered, and a contact flow that gives a visitor an obvious path to take when they are ready. Those are small choices on the surface, but together they determine whether the site feels like a finished offer or a draft that still needs translation.
What the buyer can infer
If the build is this structured for a real estate brand, the buyer can reasonably expect the same discipline in their own project: clear scope, visible milestones, and a page that is designed to support a business outcome rather than simply decorate a homepage.
The page is a sequence of decisions. What should a person see in the hero section? How much proof is enough before the visitor gets bored? Which pieces should live on the homepage and which should be split into their own route? Those questions are where the value lives, because they are the questions every serious website project has to answer.
We answered them by keeping the home experience direct and by moving secondary interactions, such as the questionnaire, into their own route. A buyer can still capture structured intake when needed, but the main page does not get overloaded trying to do every job at once. That respects how people actually scan a site: an immediate answer, then proof, then a path forward.
The same principle shows up in the contact page. Instead of hiding the next step behind a vague button, the build keeps the action visible and the form straightforward. That is a small implementation detail with large consequences for trust. A buyer can see that the system is designed for use, not just for show.
The screenshots matter for the same reason. The homepage image proves the lead framing. The pricing-page image shows the case study in context, which is important because buyers usually discover proof through a pricing or services page rather than a standalone page they seek out on purpose. The contact image completes the story by showing the handoff.
It also creates a cleaner path for distribution. A prospect can land on the pricing page, click into the case study, and see the proof in context. A newsletter reader can arrive at the same evidence from a different entry point. The strongest proof is the proof that can be linked without extra explanation.
Tanta Holdings sells a website-build service, and the first published case study has to prove that service with something more useful than adjectives. Future website-build stories can keep the same rhythm — problem, approach, result, supporting evidence — so the archive grows without reinventing the format every time.
Next step
Need this kind of proof on your own pricing page?
This case study now anchors the website-builds story on Tanta Holdings. The pricing page can send prospects here, and the newsletter can feature it from a different entry point.