Artian is hiring a Product Marketing Manager to build "case studies, proof points, and value narratives that demonstrate measurable operational impact" and vertical offerings. The proof already exists, but only as three short homepage cards: option-contract exceptions across 20+ systems at a tier-1 U.S. bank, 250+ risk data issues in one controlled workflow at a global investment bank, and more than $1M a week in overpayments identified at a health insurer. The site has 25 URLs and none of them is a use case page, so a head of trading operations or payer operations who searches for their problem, or gets a link from a Solutions Consultant, lands on a general homepage.
First action
Draft the trading operations page from the delivery notes.
How to measure it
Meetings that cite a use case page
- Now
- –
- Target
- 10 a quarter
- By
- 90 days
Steps
Collect the facts
Systems, volumes, time saved, controls, per deployment.
Solutions Delivery Manager 3 days
Agree anonymity rules
What each client allows: size band, region, numbers.
Co-Founder and CEO 1 week
Write three pages
Before, loop, controls, result.
Product Marketing Manager 1 week
Design a one-pager
PDF for each, for follow-ups.
Product Marketing Manager 3 days
Publish and link
From the homepage cards and the contact page.
Software Engineer - Solutions 2 days
Use in POCs
Open discovery with the closest page.
Founding Solutions Consultant ongoing
Track
Visits, meetings and which page.
Product Marketing Manager monthly
Why it works
Write one page per deployment with the name kept private: the exception type, the systems involved, the before (who did the work, how long, the risk), the governed loop Artian ran (detect, gather context, decide, approve, fix, log), the controls the client's risk team signed off, and the result. Add a one-page PDF version for sales, link each page from its homepage card and "Discuss a use case", and use them as the first three vertical offerings.
Regulated buyers want to see a peer's workflow, not a platform diagram, and anonymized detail is normal in banking. Three pages also give search engines and AI assistants something specific to match to "trade break remediation" or "claims overpayment" queries.
Ready to use
CopyAnonymized case study outline
Client: <tier-1 U.S. bank | global investment bank | health insurer> Exception: <option contract breaks | risk data adjustments | claims overpayments> Before: who handled it, how many systems, time per case, risk The loop: detect, gather context, investigate, decide, route for approval, fix, audit trail Controls approved: lineage, separation of duties, human approval points Result: <20+ systems orchestrated | 250+ issues in one workflow | $1M+ a week identified> Next workflow on the same foundation CTA: Discuss a use case
Risks and how to handle them
Client sensitivity
Get written sign-off on each page; use ranges if needed.
Too technical for executives
Lead with the result and keep the diagram second.
Evidence
- HiringProduct Marketing Manager (New York, Distribution team, still open): "Drive positioning and messaging"; build "pitch decks, one-pagers, competitor comparisons, product explainers, demo narratives, ROI stories"; "Build customer stories, case studies, proof points, and value narratives that demonstrate measurable operational impact"; lead GTM for "vertical-specific offerings"; support "demand generation, website messaging, thought leadership, events"; nice to have: "Familiarity with regulated enterprise buying processes, risk, compliance, operations, procurement, or security review".Source
- Your websiteHomepage: "Automation stops at exceptions. Artian doesn't." Three deployments with numbers: trading operations, option contract exceptions "orchestrated across 20+ systems"; risk operations, "More than 250 risk data issues and adjustments run through one controlled workflow"; payer operations, "more than $1M in savings identified each week". Named only as "A tier-1 U.S. bank", "A global investment bank" and "A technology-forward health insurer": "We keep our clients' names off our site." Calls to action: "Discuss a use case" and "Talk to our team".Source
- Your websiteSitemap (25 URLs, checked November 4, 2026): 17 blog posts plus the homepage, Governance, Company, Careers, Contact and three legal pages. No page for any use case, solution or industry. Overlapping posts: "From Vibe Coding to Cognitive Overload" and "Vibe Coding Will Break Your Enterprise"; "The Swan Effect: What Banks Really Look Like Beneath the Surface" and "Engineering Hidden Below the Surface".Source
- HiringFounding Solutions Consultant (posted October 14, 2026): qualifies "on workflow complexity, business value, and technical fit"; delivers demos "tailored to each customer's workflows"; scopes "POCs with clear objectives, success criteria, milestones"; builds "repeatable discovery frameworks, POC structures, demo environments, and solution templates"; strongly preferred: experience "navigating enterprise security, architecture, model risk, or governance reviews".Source