A Sudanese fintech company: a website and CMS structure for institutional buyers

The company's website needed to do more than announce a company. It had to explain a complex financial-infrastructure offer to people who would arrive with different questions: banks evaluating partnership risk, public institutions looking for payment modernization, and private partners trying to understand where the company fits in the ecosystem.

Context and scope

The source material included old-site notes, new-site planning, visual direction, company profiles, proposal material, and sector-specific decks. The challenge was to turn that into a clean site architecture instead of copying a proposal onto the web. The site needed a CMS structure so the team could add use cases, partner materials, and updates without breaking the narrative every time.

What I built

I defined the page logic around buyer questions: what the company does, where it operates, which financial problems it solves, how the technology and governance work, and how a bank or public entity can engage. The CMS structure separated evergreen company content from changeable proof: solutions, profiles, news, proposals, and sector pages. That made it possible to keep the public story stable while letting the business publish new materials as partnerships evolved.

Design choices

The site structure avoided a generic tech-company pattern. A payments company serving institutional stakeholders needs clarity before personality. Pages were arranged around trust, use cases, and implementation readiness. I kept room for SDD as a product/platform story without making the parent company disappear behind a single app. The content model also supported bilingual presentation, because formal stakeholders often move between Arabic and English during evaluation.

What changed

The company gained a web plan that matched how the business actually sells: through credibility, structured explanation, and specific partnership scenarios. The CMS logic reduced the risk of every update becoming a mini-redesign. It also made the website a home for the same language used in profiles and pitch decks, which kept the brand system coherent.

Takeaway

For institutional services, a website is a decision-support system. The company's web and CMS work turned scattered materials into a public structure that could grow with the company without losing the plot.