Technical Account Manager, Enterprise Implementation.

Full-time · Remote · Based in the Americas, North or South, within ~2 hours of US Eastern

Archilogic is the spatial system of record for the age of AI: buildings, the world's largest asset class, become structured data every system, team, and AI agent can reach. Floor plans in CAD and PDF turn into a live, queryable spatial database, edited in the browser and versioned like code. We're already the spatial source of truth for some of the world's largest enterprises, remote-first with hubs in Zurich and the San Francisco Bay Area.

Why this role

When an enterprise customer signs, the next few months decide whether the account thrives or churns. You own that outcome. You are the person who turns a signed contract into a customer who is genuinely successful on the platform, and who renews and expands.

Your customers are workplace, corporate real estate, and facilities teams within some of world's largest companies: the people who run buildings. You will learn how each of them actually works, set up their account to match, teach their team until the product is part of their week, and stay close to the account as its trusted technical contact. When configuration is not enough, you build the thing that solves it yourself, with our SDK and APIs and with engineering behind you for anything deep.

This is a customer role with a builder's hands. If you have been the person on the account who ends up writing the script, wiring up the integration, or building the dashboard because it was faster than waiting, you will do well in this job.

What you'll do

• Own enterprise onboarding and adoption end to end: configure each customer's account around their real workflows, get their team live, and drive usage across the accounts you manage. These are your accounts and your numbers.
• Run implementations yourself: discovery, data model, account setup, go-live, and the follow-through that makes it stick.
• Teach and enable users: train facility managers, workplace teams, and IT until the product is embedded in how they work.
• Be the trusted face of Archilogic for your accounts: regular check-ins, first-line support, renewals and expansion conversations, escalating deep backend work to engineering.
• Make the data model fit how the customer actually operates, so Archilogic becomes their source of truth.
• Get hands-on with the platform when a customer needs more than configuration: small scripts against our APIs, and building or adapting extensions with our SDK (JavaScript/TypeScript).
• Turn recurring customer friction into roadmap signal for product.
• Support pre-sales conversations with scoping and hands-on product walkthroughs when a deal needs validation.

What you'll bring

• 
  
• Ownership of enterprise customer relationships and their outcomes with a technical product. Customer success, technical account management, implementation, professional services, or solutions delivery. You can point to accounts you kept, grew, and got live, and you know your own numbers: retention, adoption, expansion, time to value. 
• Hands-on technical ability, at the level of someone who builds small things well: Concretely: you have written SQL against a real database, tested or configured an API integration, automated something with a script, or built a dashboard or workflow that other people then relied on. Customers will depend on what you set up, so it has to work.
• The instinct to teach: You can make a non-technical operations person comfortable with a technical product, and hold a credible conversation with their engineers in the same day.
• Judgment and ownership: you're comfortable owning ambiguous problems on a small, remote team without leaving a mess behind.
• Comfort using AI tools (Claude, Codex, MCP, agentic tooling) as part of daily work.

Nice to have

• Familiarity with the world our customers live in is a big plus: IWMS/CAFM platforms (Tririga, Archibus, Planon, ServiceNow), CAD/BIM or floor plan data, corporate real estate or workplace operations. It's not a requirement and we'll teach you the domain, but if you already speak this language you'll be effective much faster. Tell us about it when you apply.

• Experience at a B2Enterprise SaaS platform with an extension or SDK ecosystem.
  

If you meet most of what is above but not all of it, please apply anyway. We would rather read your application than have you screen yourself out.

Two things this role is not

It is not a software engineering job with customer calls attached. And it is not a customer success role where someone else does the technical work. The person who thrives here sits genuinely in the middle.

Location & eligibility (please read before applying)

• You must be based in the Americas within ~2 hours of US Eastern time (US Eastern/Central/Mountain, Canada, Latin America). US Pacific and locations outside the Americas are outside our collaboration window.
• We are not able to sponsor visas or work permits, now or in the future.

Compensation is location-tiered: the range depends on where you're based, and we share it early in the process.