Interactive demo showcases revenue-based lending capabilities of universal API
A small-business data API company ups its sales game thanks to a new demo-able UI/UX, which helps prospects visualize the revenue-based financing journey from inquiry to approval
UI Design & Dev for small business data API company
- 250 employees
- ClickModel® Prototype
- Branding & UI/UX Design
- Development & Deployment
When your product is technical and fully white-labeled for an end user—like Codat’s universal API—it can be a challenge for prospects to quickly conceptualize the value it can provide. Praxent’s demo enables them to see the solution in the context of a real-life customer.
Codat provides real-time connectivity to business accounting, banking, and commerce data that enables software providers and financial institutions to build integrated products for their SMB customers. Their clients range from lenders to corporate card providers. Business forecasting tools and use cases include automatic reconciliation, business dashboarding, and loan decisioning.
Praxent designed a compelling demo to help prospective buyers better understand how revenue-based financing works by seeing Codat’s capabilities in action, thereby proving the technical viability of its platform and creating a positive brand perception.
The client came to Praxent wanting to enable easier and more effective conversations with prospects about their API-first platform. In order to do that, they needed a way to help them visualize—by showing, not simply telling them about—how revenue-based financing works from the perspective of a fintech/neobank.
They engaged Praxent to design and build an interactive (clickable), demo-facing interface for a fictional fintech brand that had to be simultaneously aspirational and relatable.
The team had technical leadership but lacked the in-house resources to design the UI/UX and build the prototype.
Codat was seeking to bring on a trusted design and development team to work with them on this prototype as a way to advance the relationship.
How we helped
Praxent applied Codat’s design brief and findings from an in-depth branding workshop to create a fictional brand, for which it designed and built a fully interactive prototype consisting of a landing page and several high-fidelity screens.
Matching the clean, modern look and feel of a real fintech brand, the demo enables prospects to simulate the revenue-based financing journey, including running the software, pulling data, and displaying loan options based on actual sales data for the fictional brand.
Praxent staffed two project managers, three engineers, and two designers.
Led by Codat’s Lead Solutions Engineer and Praxent’s principal delivery lead, the team met daily internally to communicate progress and remove blockers. They met weekly with the client to present designs.
They performed beyond expectations from a project management perspective. They were always clear about where we were from a development standpoint and had weekly status updates along with documented updates.
Lead Solutions Engineer, Codat
Praxent created an interactive prototype to demonstrate the visual design and usability of Codat’s platform. Codat’s solution engineers now have a way to showcase the platform’s capabilities and prove the viability of its technology by walking a prospect through how a fictional, but believable, fintech would leverage its eCommerce integrations.
By presenting a fictional brand with the same UI/UX polish of a modern fintech or neobank brand, it implies Codat’s technology is also modern, built to power the next generation of fintech platforms.
Working together on a prototyping engagement furthers the working relationship between Codat and Praxent.
Principal Delivery Lead
Senior Delivery Lead
Senior Quality Assurance Analyst
Associate Technical Director
Senior DevOps Engineer
Associate Software Engineer
Principal Product Designer
Associate Product Designer
What Codat had to say
What was the scope of their involvement?
We gave them a general outline, and our goal was to make this feel like any revenue-based journey in the market. We didn’t want it to be cutting-edge because we weren’t looking to outcompete any of our buyers, but we wanted potential buyers to recognize the platform was almost state-of-the-art when we were showing off the demo. The design was completed using Figma.
What was the team composition?
We worked with two project managers, three engineers, and two designers.
How did you come to work with Praxent?
I believe someone at our company met someone from Praxent at an in-person event. Our company came to the conclusion that this would be a good way to build our relationship. We thought this would provide us with an asset, and if we decided to work together in the future, we would already know how to work together. Praxent would also have experience using our platform at that point.
What evidence can you share that demonstrates the impact of the engagement?
We were looking for three things from this project: a landing screen, an authentication screen, and a load option screen. Once those three things were delivered, we considered the project a success.
How did Praxent perform from a project management standpoint?
They performed beyond expectations from a project management perspective. They were always clear about where we were from a development standpoint and had weekly status updates along with documented updates. When our company had to take action on a piece of the project, Praxent followed up with us in a timely manner. We connected their teams with our infrastructure via GitHub and communicated through phone calls and email.
What did you find most impressive about them?
Their team had a lot of enthusiasm, which let us know they were excited about the project. We enjoyed interactions with Praxent and communicated effectively. We were very happy with everything delivered, and they came up with a great design, given the brief we gave them.
Are there any areas they could improve?
We wish they could have coordinated a deployment plan and timeline more thoroughly.
Do you have any advice for potential customers?
Bring as much as possible into your specific requirements because they’ll consider that. If there’s anything specific you’re looking for, bring it up, and get input from members of your team to end up with the product that will meet most people’s needs.