George Matelich

Product/Growth Generalist

Rely

Generalist / Founding
Posted by George Matelich

Overview

You're the generalist hire at a 7-person seed-stage startup. Your job is to take on whatever's blocking growth - customer onboarding, product feedback loops, internal tooling, light customer success work, growth experiments. You switch contexts frequently and own projects end-to-end without clear lanes.


Role Snapshot

AspectDetails
Role TypeGeneralist (product/growth/ops hybrid)
Sales MotionN/A - not a sales role
Deal ComplexityN/A
Sales CycleN/A
Deal SizeN/A
Quota (est.)N/A - success measured by projects shipped and problems solved

Company Context

Stage: Seed (7 employees total)

Size: 7 people

Growth: Deal volume up 4x week-over-week - infrastructure and customer support needs growing fast

Market Position: Category creator in multifamily real estate due diligence automation


GTM Reality

Not a GTM role, but you'll work closely with sales and customers:

  • Help onboard new customers and troubleshoot their first uploads
  • Collect feedback from prospects and customers to inform product roadmap
  • Build internal tools or workflows that help the sales team close faster

Competitive Landscape

Main Competitors: Manual processes, generic document AI tools

How They Differentiate: Purpose-built for real estate due diligence workflows

Common Objections: (Not directly your concern, but you'll hear them from customers)

Win Themes: Speed, accuracy, scalability


What You'll Actually Do

Time Breakdown

Customer-Facing (40%) | Product/Internal Tools (35%) | Data/Analytics (25%)

Key Activities

  • Customer Onboarding: Walk new customers through their first document uploads. Troubleshoot when their files don't process correctly. Answer questions about output formats and integrations. You're in Slack/email with customers daily.
  • Product Feedback Loop: Collect pain points from sales calls, customer conversations, and support tickets. Synthesize patterns and work with founders to prioritize what to build next. Document feature requests and edge cases.
  • Internal Tools/Workflows: Build or improve internal processes - maybe a CRM setup, a dashboard to track deal volume, scripts to automate repetitive tasks, or onboarding templates. Whatever's slowing the team down.
  • Growth Experiments: Test acquisition channels (content, partnerships, SEO), analyze what's driving signups or demos, run small experiments to improve conversion rates. This is scrappy, not polished growth marketing.

The Honest Reality

What's Hard

  • No clear job description. Priorities change weekly based on what's urgent. You need to be comfortable with ambiguity.
  • Context switching constantly. You're jumping from customer issues to data analysis to product spec writing. Hard to get deep focus time.
  • Founder-stage chaos. Things break, plans change, you're often figuring it out as you go.
  • Limited resources. You don't have a team or budget. You're scrapping together solutions with free tools and elbow grease.
  • Customer issues escalate quickly. When something breaks for a customer mid-deal, you're the one figuring it out under time pressure.

What Success Looks Like

  • Customers onboard smoothly without founder involvement
  • Product feedback gets organized and prioritized, not lost in Slack threads
  • Internal tools/workflows save the team 5-10 hours per week
  • Key metrics (activation rate, retention, NPS) trend upward due to your work
  • Founders trust you to own problems end-to-end without hand-holding

Who You're Selling To

N/A - but you work closely with:

  • Multifamily asset managers and acquisitions teams (your customers)
  • Internal team (founders, AE, engineers)

What They Care About:

  • Customers: Fast onboarding, accurate outputs, responsive support
  • Internal team: Clear feedback, efficient processes, fewer fires to fight

Requirements

  • 2-4 years experience in product, operations, customer success, or growth at an early-stage startup
  • Comfortable with ambiguity and changing priorities
  • Technical enough to use APIs, write SQL, or build simple internal tools (or learn quickly)
  • Strong bias to action - you see a problem and fix it without waiting for permission
  • Customer empathy - you genuinely want to understand their workflows and pain points
  • Startup experience preferred (you've lived through 0→1 chaos before)