Introduction
What is Tabono — and why does the name matter?
Tabono is an Adinkra symbol from West African tradition — a paddle or oar, representing the strength, hard work, and persistence required to move forward together. For a company built on mining, industrial, and logistics expertise across African markets, the name carries real weight. It wasn't chosen arbitrarily, and a website that failed to honour that meaning would have failed the brand entirely.
When founders Liran and Reon came to BrandingLab, they didn't arrive with a relaxed brief and an open timeline. They arrived with a conference date — their annual industry event — and a clear message: the site needed to be live, impressive, and doing its job before their attendees walked through those doors. We had three weeks.
What did Tabono need their website to achieve?
Tabono operates across three demanding sectors — mining technology, industrial services, and logistics systems. Each involves complex offerings that take real expertise to explain clearly. Their audience includes senior industry operators, potential partners, and investors who read between the lines of how a company presents itself online.
The brief had two simultaneous requirements that rarely sit easily together. The site needed to communicate global capability — professional, internationally credible, able to hold its own against any competitor anywhere. And it needed to be unmistakably, proudly African — not as an aesthetic gesture, but as a genuine expression of where Tabono comes from and who they are building for.
And it needed to launch in three weeks, with twenty-plus pages, in time for the conference.
Project: Tabono — brand expression and full Webflow website
Founders: Liran and Reon
Sectors: Mining technology · Industrial services · Logistics
Duration: 3 weeks
Deliverable: 20+ page Webflow website with animation system
Live: tabono.com
Challenge
What made the Tabono brief genuinely difficult?
There are challenging projects, and then there are projects where every variable is hard at the same time. Tabono was the latter.
When Liran first walked us through the timeline, the internal reaction was something close to alarm. Three weeks. Twenty-plus pages. A conference date that existed independently of how the website was progressing — it wasn't moving, it wasn't flexible, and Liran was clear: "Miss this, and we're toast."
The specific constraints stacked on top of each other:
- Timeline vs. scope mismatch. A 20+ page website with a custom animation system would normally take six to eight weeks with comfortable review cycles. We had three. That's not just a tight schedule — it's a fundamentally different way of working, where the usual process of design, review, revise, approve, build can't happen sequentially.
- The "wow factor" brief. Liran and Reon wanted something that would make conference attendees stop and look. That's one of the hardest briefs to execute — "impressive" is subjective, and in a deadline environment, the temptation is to default to safely professional rather than genuinely memorable. We had to find something that was both.
- Industrial complexity without industrial dullness. Mining technology, logistics systems, and industrial services are not sectors known for exciting web design. Communicating the genuine technical depth of Tabono's offerings without producing a site that made visitors' eyes glaze over required real editorial judgment at every page.
- African identity at global standard. This is a design challenge that can go wrong in two directions. Lean too hard on African visual motifs and the site looks like a cultural exercise rather than a business. Ignore the heritage entirely and you've missed what makes Tabono distinct. The brief required finding the precise point between those two failures.
- Performance under pressure. The site would be launched at a conference. Attendees would be looking at it on mobile devices, hotel WiFi, and exhibition hall connectivity. Every animation and transition had to be built to work under those conditions — not just under ideal circumstances in a design studio.
Why is designing for African industrial businesses uniquely demanding?
African industrial companies operating at international scale face a representation challenge that most Western businesses don't encounter: they need to communicate local expertise and authentic identity to domestic partners, while simultaneously signalling global credibility to international clients and investors who may carry unconscious assumptions about African businesses. Getting both audiences to feel correctly addressed by the same website requires design and editorial decisions that go well beyond surface aesthetics.
Approach
How do you build a 20-page website in three weeks without cutting corners?
The honest answer is: you don't work sequentially. You can't afford to. The standard design process — finalise design, get approval, start building, review, revise — assumes time that a three-week conference deadline doesn't provide. We threw that process out and rebuilt it around parallel workstreams.
Our lead designer Tom essentially lived in Figma for the first two weeks. By his own admission, he was dreaming in colour palettes by the end of it. But that level of intensity is what the brief required — you don't find a visual system that threads the needle between industrial seriousness and African identity by working conservative hours.
What does designing for African heritage and global credibility actually look like in practice?
The visual system we developed didn't try to explicitly reference Adinkra symbols or traditional African motifs — that route leads quickly to decoration that feels applied rather than authentic. Instead, we worked from the underlying principles: geometric precision, bold structural forms, a colour palette derived from the earthy, rich tones of African landscapes and materials, combined with the clean typographic hierarchy of internationally credible business design.
The result was a visual identity that felt unmistakably grounded in African design sensibility without announcing itself as such. Visitors who know that visual tradition recognise it. Visitors who don't see a confident, internationally credible industrial company. Both readings are correct.
How did parallel workflows make the three-week timeline possible?
While Tom was still finalising design decisions for the later pages, our development team had already started building the core site architecture and the earlier sections in Webflow. This meant accepting a calculated risk: we were sometimes building to designs that weren't fully locked. If a design direction changed late, sections would need to be rebuilt.
The mitigation was communication. Tom and the development team were in near-constant contact — not reviewing completed work, but collaborating on work in progress. Design decisions were made with an eye on what was already built. Build decisions were made with an eye on where the design was heading. The usual wall between design and development came down entirely.
How were the animations built to survive a conference environment?
Conference conditions are a worst-case scenario for web animation: mobile devices with varying processing power, unpredictable network connections, and no guarantee of the screen quality you designed for. Every animation in the Tabono site was tested specifically under these constraints.
We used hardware-accelerated CSS transitions and GSAP where needed, keeping JavaScript animation payloads small and prioritising CSS-driven effects wherever possible. Load sequences were staggered so that content appeared progressively rather than waiting for everything to be ready — meaning that even on slow connections, the site felt like it was working confidently rather than struggling.
The 20+ pages were built with a shared component library, so performance optimisation applied globally rather than needing to be repeated per page. When Tom got the mobile menu glitch the night before launch, it was caught and fixed in under two hours precisely because the architecture was clean enough to diagnose quickly.
Feedback
What happened the night before the conference launch?
The night before Tabono's annual conference, the BrandingLab team was still online. There was pizza. There was a mobile menu glitch that appeared at 11pm and required two hours to track down and fix. At 2am, with the conference starting in a few hours, we pushed the final version live and signed off with high-fives — the kind that feel genuinely earned.
That sequence is worth understanding as a feature of how BrandingLab works, not a flaw in the process. A three-week deadline for a 20+ page website means you are optimising for launch. Something will need to be fixed close to the wire. What matters is that the team is there to fix it, the architecture is clean enough to make the fix straightforward, and the overall site is ready to perform when it matters.
What did the conference audience experience?
Tabono's attendees arrived at the conference with a website that matched the ambition of the company they'd come to engage with. The site communicated exactly what Liran and Reon needed it to communicate: that Tabono is a serious, internationally capable operation with deep roots in African industrial expertise.
The "wow factor" brief — that elusive combination of visual impact and functional credibility — was met. The animations ran. The mobile experience held up. The conference launched on time.
What does this project demonstrate about working under genuine time pressure?
The Tabono project is a useful reference point for any organisation that needs a high-quality website quickly. Not because we recommend three-week timelines — we don't. But because it demonstrates that BrandingLab can operate under that kind of pressure without compromising on what matters: design quality, technical performance, and the alignment between what a brand is and how its website represents it.
The combination of parallel workflows, a shared component architecture, and a team willing to be online at 2am when it counts is what made it possible. That's not a process you can document in a methodology document. It's a way of working that either exists in a team's culture or it doesn't.
FAQ
How quickly can BrandingLab deliver a website for a hard deadline?
The fastest project BrandingLab has delivered was a focused single-page site in eight days. The Tabono project — a 20+ page website with a custom animation system — launched in three weeks to meet a conference deadline. Compressed timelines are achievable but require parallel workflows, fast decision-making from the client, and a team willing to work intensively. Scope and timeline are directly linked: the tighter the deadline, the clearer the brief needs to be from day one.
What do mining, industrial, and logistics companies need from a website?
Industrial B2B websites face a specific challenge: communicating genuine technical complexity in a way that doesn't lose non-technical decision-makers. The most effective approach separates the "what we do" layer (accessible to any visitor) from the "how we do it" layer (detailed enough for technical evaluators). Navigation should reflect the different mental models of founders, investors, and operational partners — because these audiences are reading the same site with different questions in mind.
How do you design a website that honours African heritage without it feeling like a visual exercise?
The risk with culturally grounded design is that it becomes decoration — African motifs applied to a generic template. The better approach works from underlying principles: the geometric precision, structural boldness, and earthy palette of African design traditions translated into a system that functions at international business standard. The result should be recognisable to people who know that visual culture, and simply feel confident and credible to those who don't. Applied decoration announces itself; authentic grounding is felt rather than seen.
How does Webflow handle large multi-page sites with custom animations?
Webflow scales well for 20+ page sites when built on a component-based architecture — reusable elements that are styled once and applied globally. For animation systems, BrandingLab uses GSAP hosted via CDN alongside Webflow's native interaction engine, with hardware-accelerated CSS transitions for lightweight motion. The result is a site that performs well across devices and connection speeds without needing ongoing developer maintenance to keep it running.
What should a company prepare before starting a fast-turnaround website project?
Three things determine whether a compressed timeline project succeeds: clear brand direction (no major identity decisions in the middle of the build), decision-making speed (one or two people with authority to approve, not a committee), and content readiness (copy and imagery can't wait until the end). For the Tabono project, Liran and Reon moved fast on feedback and kept approval chains short — that discipline on the client side was as important as BrandingLab's parallel build process in hitting the conference deadline.
Can you build a website to launch at a specific event or conference date?
Yes — event-driven launches are a project type BrandingLab has experience with. The key difference from a standard project is that the launch date is fixed, which means scope has to flex rather than timeline. If new requirements emerge mid-project, they're scheduled for a post-launch update rather than delaying the launch. This requires agreement from the outset that "live and 95% there" at the conference beats "perfect but late."
