.svg)
We use your actual service descriptions and transaction examples to define the website structure. Copy development and design establish how different mandate types, sector teams and deal roles should appear before the Webflow build. The agreed CMS gives your team a consistent way to maintain that record as new announcements and people are added.
We review capabilities, target mandates, sector teams and representative transactions. Two entries with different bank roles help establish the distinctions the site must retain, alongside the public records and source material available for migration.
Figma designs test the service, sector, banker and transaction pages together. We check different announcement formats and mobile layouts, including financings with several participants and transactions where no value has been published.
We build the agreed Webflow collections, relationships and page designs for the public site. Transaction search, filters and any external source are defined against the record set before implementation, rather than assuming every library needs the same functionality.
We review transaction attribution, service relationships, biography details and contact destinations with your team. Testing covers different record lengths and public-data states as well as mobile browsing, document links and the agreed inquiry behavior.
Your team learns how to add approved deal records and maintain banker profiles within the agreed CMS. We demonstrate the role, service and sector fields so future announcements can appear consistently in the relevant parts of the site.
.png)
.png)
.png)
.png)
.png)
.png)
