["Full-Time"]
Remote
SaaS
jobicy
About this role
Mactores is the agent-native AWS modernization firm. We ship AWS modernization to production in weeks, data platforms migrated, legacy applications and databases refactored, AI agents running against real data, for mid-market and lower-enterprise companies in financial services, healthcare and life sciences, internet and software, manufacturing, and TMEGS.
Our delivery model is built around AI agents that absorb the repetitive 60–70% of engagement work, discovery, schema mapping, validation, test generation, cutover rehearsal, that traditional consulting bills against human hours. Forward-deployed engineers work on top of those agents, embedded with the customer's team, owning architecture, judgment, and cutover.
We commit to a fixed delivery date on a fixed fee. If we slip for reasons inside our control, the cost sits with us. Most modernization doesn't ship. Ours does. That is the entire pitch. You'll be the named Mactores contact for AWS sales teams across US territories.
AWS account managers, ISMs, partner-development managers, and specialist sellers each carry a partner deck full of firms that all say roughly the same thing. Your job is to make them see Mactores as the agent-native firm in that mix, the one they route to when their customer needs a modernization program finished, not staffed.
What you'll sell maps directly to what AWS reps care about: we're MAP-eligible, AWS Agentic AI Specialized, and predictable on fixed-date engagements. Our founders built the agent platform we deploy, so deployment depth is a structural advantage and AWS reps make money when we win. The conversation starts on the same side of the table.
You won't run deep technical demos, a forward-deployed engineer does that. You set up the meeting, frame the customer's problem, walk through the agent-native approach in business terms, anchor everything in shipped case studies, and hand off to the FDE when the conversation reaches architecture. Then you close the loop: register the opportu
Selling Motion
Sales Cycle
Enterprise
6–18 month cycles, complex multi-stakeholder deals
Prospecting
Channel / Partner
Sell through partners, resellers, or alliances
Buyer Persona
C-Suite
Selling to executive decision-makers
Requirements at a Glance
Typical Day — BDR
Estimates based on role type and selling motion — actual may vary by company.
SaaS — Interview Intel
Typical Sales Cycle
30–90 days (SMB) · 3–9 months (Mid-Market) · 6–18 months (Enterprise)
Common Buyer Objections
- "We're locked into a contract with [competitor]"
- "We built something in-house already"
- "We don't have budget until next quarter"
- "Our team won't adopt another tool"
Key Industry Metrics
Hot Topics to Reference
- • AI-native product disruption
- • PLG vs sales-led motion debate
- • Vertical SaaS consolidation
- • Usage-based pricing models
Use these insights to speak the buyer's language in interviews.
Tags
How do you qualify inbound leads?
Template questionDescribe your approach to multi-threading into an account.
Template questionHow do you prioritize your pipeline?
Template questionExpect high-volume outreach activity with success measured by meetings booked and pipeline generated.
Top SaaS reps often earn significant upside through accelerators once quota is exceeded.
This remote-friendly role provides geographic flexibility while maintaining access to a SaaS market.
Are you a closer?
Interested in SaaS? Build your profile to get matched with roles like this.
Explore More Sales Jobs
Similar Roles
Browse More Jobs
Ready to land your next closing role?
Build your free closer profile to get matched with high-ticket sales opportunities, track applications, and showcase your track record.
Join 500+ closers already on the platform • Free forever
