Baseten is hiring a Solutions PMM to compete in Financial Services, but the page buyers would find today is a stub: the title is "Financial services", the description is "Baseten for financial services", and the only call to action says "Click here". The Healthcare page next to it shows what a finished industry page looks like.
First action
Copy the Healthcare page template and write the five use cases and the risk-team answers in one document.
How to measure it
Qualified meetings sourced or touched by the page
- Now
- –
- Target
- 8 a quarter
- By
- 1 quarter
Steps
Pick the use cases
Five financial-services workloads Baseten already runs or has been asked about, from the CRM and SA notes.
PMM, Solutions 1 day
Write the risk answers
Data handling, deployment options, compliance, uptime and audit, in the order a bank's review asks them.
PMM, Solutions 1 day
Find one proof point
A named or anonymised financial-services workload with one number, cleared with the customer or legal.
AI Native Sales Manager 3 days
Build the page
Healthcare template, real meta title and description, one H1, Talk to an engineer.
Web team 2 days
Add it to the menu
Industries: Enterprise, Healthcare, Financial services.
Web team 30 minutes
Hand it to sellers
Send to Enterprise and Strategic AEs with a two-line cold email that links to it.
PMM, Solutions 1 hour
Why it works
Rebuild /financial-services/ on the Healthcare page's structure: three to five use cases a bank, insurer or asset manager would recognise (document and research, call transcription and summarisation, fraud and KYC review, coding agents for internal engineering), the compliance and deployment answers a risk team asks first (SOC 2 Type II, self-hosted and region-restricted deployments, data never stored), one proof point, and "Talk to an engineer". Add it to the Industries menu.
An industry page is the first thing a Strategic or Enterprise AE sends after a cold call, and the first thing a bank's architect checks before replying. A stub tells them Baseten has not sold to anyone like them yet.
Ready to use
CopyFinancial services page outline
Title: AI inference for financial services | Baseten H1: Production AI for banks, insurers and asset managers 1. Use cases: research and document agents; call transcription and summaries; fraud and KYC review; coding agents for internal teams; customer service voice agents 2. What your risk team will ask: where data goes (never stored), where it runs (our cloud, your VPC or hybrid), compliance (SOC 2 Type II), uptime (99.99%), access (RBAC, audit) 3. Proof: one workload, one number 4. Talk to an engineer
Risks and how to handle them
No public financial-services customer yet
Use an anonymised workload and the compliance answers until a named story is approved.
Claims a bank's legal team would challenge
State only what the trust center and contracts support, and link to them.
Evidence
- Your websiteThe /financial-services/ page is in the sitemap but is a stub: its title is "Financial services", its meta description is "Baseten for financial services", and under the heading "Baseten for financial services" the only call to action reads "Click here", followed by the generic product block. The Healthcare page, by contrast, has use cases, HIPAA and SOC 2 Type II, 99.99% uptime and an OpenEvidence quote. The site's Industries menu lists Enterprise and Healthcare, not Financial Services. The Enterprise page says "Baseten never stores the inputs or outputs of your inference requests".Source
- HiringProduct Marketing Manager, Solutions: "define and own Baseten's up-market, enterprise, and industries go-to-market strategy", build "the vertical go-to-market strategies that let us compete in Financial Services, and Health & Life Sciences"; own industry landing pages, TCO/ROI guides, pricing guides, one-pagers and ABM experiments; "largely greenfield".Source
- Your websitePricing: Basic is "$0 per month, pay as you go"; Pro adds priority GPUs and Slack support; Enterprise adds "Use existing cloud commitments", "Full control over data residency", self-hosting and custom regions. Model APIs are priced per million tokens, for example GLM-5.3 at $1.40 input and $4.40 output and DeepSeek V4.1 Flash at $0.30 and $1.20.Source