Case Study · Pentathlon Ventures
A VC site that's always ready for the next first impression.
For Pentathlon Ventures, the website is the first filter. Founders check it before applying. LPs check it before taking a meeting. It needs to work perfectly, every time, for the most discerning audiences in the business.
8hrs/mo
Saved per month. Hours that go into sourcing.
99.97%
Uptime over 6 months
0
Emergency calls in 6 months
Objectives
Two flows that have to work on the first try.
Pentathlon needed two paths held to a standard: the two-click deck download and the two-click founder application. Both were designed to remove friction, and both are used once by people who will not report a problem if they hit one. The brief was to make sure neither ever fails silently, on any device, at any hour.
Before NoDrama
When your audience is LPs and founders, "mostly working" is not a category.
Pentathlon's site was built with a clear purpose: communicate a philosophy-first VC brand to two very specific, very discerning audiences. The two-click deck download and two-click founder application flow were designed to remove every possible point of friction.
That friction comes back fast if the site is not actively maintained. A broken application flow means founders apply elsewhere. An LP who hits a slow site at midnight before a morning meeting draws a conclusion.
NoDrama's job is simple: make sure none of that ever happens.
The honest audit
What we found when we looked.
What NoDrama's onboarding audit found on a newly launched site where first impressions are the product.
No staging environment.
The application flow and deck download links went live on every update with no safety net. A broken link in either flow is invisible until a user reports it.
No uptime monitoring.
Any downtime would be discovered by a team member, or worse, by a founder mid-application or an LP the night before a meeting.
Four plugins with pending major version updates.
One touched the application form handler. Needed the form checked before and after the update.
Deck downloads are linked to a single hosted asset with no redundancy.
A URL change would silently break it, no alert, no fallback.
Mobile performance not baselined.
A significant portion of founder traffic arrives via mobile from LinkedIn. Load time on key pages had not been measured post-launch.
The work
What we actually did. Specifically.
Audit and brief.
Full audit. The deck and application flow were tested manually. Five items prioritised and documented.
Update checks and uptime monitoring.
Before-and-after update checks configured. Uptime monitoring is active with 60-second alerting. The deck download link is secured with a redundant hosted asset.
Checked plugin updates.
Updated all four pending plugins, with the application form and deck download flow checked before and after. Zero issues.
Mobile performance.
Baselined mobile performance. Compressed hero assets and configured lazy loading. Load time on mobile cut from 4.8s to 2.1s.
Weekly cycle and monthly flow tests.
All updates run with 18 key pages photographed before and after. Application and deck download flows are manually tested monthly. Report on the 1st.
The results
6 months in.
8hrs/mo
saved per month. Hours that go into sourcing and portfolio, not site admin.
For a team whose value is in the quality of their decisions and relationships, not in website maintenance.
99.97%
Uptime over 6 months.
Ready for every LP or founder who visits.
0
Emergency calls in 6 months.
Zero is the goal. That is the whole goal.
2.1s
Mobile load time.
Was 4.8s. Fixed during onboarding.
Business outcome
What the reliability actually bought them.
Because both critical flows were monitored and tested monthly, founders who came to apply could apply, and LPs who came to read the deck could read it on the first attempt. Pentathlon kept the site working as a filter rather than a source of friction, and no inbound application or download had to be recovered manually after the fact.
NoDrama Plan
The Higher Standard
$249/mo · cancel anytime · setup free on yearly plan
Start with The Higher Standard- Backups every 12 hours, kept 90 days
- Key pages photographed before and after every update
- Global CDN, caching and image optimization
- Two small jobs at once
- 2-hour response if down or hacked
- Real restore tested twice a year