VP of Internal Systems & IT

Stord is The Consumer Experience Company, powering seamless checkout through delivery for today's leading brands. Stord is rapidly growing and is on track to double our revenue in the next 18 months. To meet and exceed this target, Stord is strategically scaling teams across the entire company, and seeking energetic experts to help us achieve our mission. By combining comprehensive commerce-enablement technology with high-volume fulfillment services, Stord provides brands a platform to compete with retail giants. Stord manages over $10 billion of commerce annually through its fulfillment, warehousing, transportation, and operator-built software suite including OMS, Pre- and Post-Purchase, and WMS platforms. Stord is leveling the playing field for all brands to deliver the best consumer experience at scale. With Stord, brands can increase cart conversion, improve unit economics, and drive sustained customer loyalty. Stord’s end-to-end commerce solutions combine best-in-class omnichannel fulfillment and shipping with leading technology to ensure fast shipping, reliable delivery promises, easy access to more channels, and improved margins on every order. Hundreds of leading DTC and B2B companies like AG1, True Classic, Native, Seed Health, quip, goodr, Sundays for Dogs, and more trust Stord to deliver industry-leading consumer experiences on every order. Stord is headquartered in Atlanta with facilities across the United States, Canada, and Europe. Stord is backed by top-tier investors including Kleiner Perkins, Franklin Templeton, Founders Fund, Strike Capital, Baillie Gifford, and Salesforce Ventures. The Opportunity Stord is made up of two complicated businesses under one roof. We build and run software at scale, and we operate an international, multi-site fulfillment and parcel network. Our enterprise systems have to carry both, which makes them as complex as anything in the product. These systems were built for a smaller company than the one we are now. This role is responsible for elevating this system. There are two direct domains. Business Operations owns the enterprise systems Stord runs on, the processes sitting on top of them, and the quality of the business data inside them. IT owns identity, devices, access, and end-user experience for a company adding headcount monthly, as well as the physical network and device infrastructure inside every fulfillment and parcel site we run. In partnership with Procurement you own Stord's SaaS estate company-wide. Engineering's tooling is also in that scope: R&D chooses it, you administer it. You report to the SVP of Product & Engineering, sit alongside the Head of Engineering, the VP of Data, and the VP of Security as peers, and work daily with leadership across Finance, Revenue, People, Legal, and Operations. This is not a blank slate, nor should you want one. What currently exists is here because it has to be: we are already a scaled operation, billions in GMV across hundreds of brands, and the systems carrying that are load-bearing. You inherit a capable team and a stack that works. What’s missing is architecture, clear ownership, and someone with a point of view on both. The test is what comes next. Taking an operation already at this scale and building it for the future, without slowing anything down. Plenty of leaders can add control to a fast company. We are hiring the one who can add control while maintaining necessary speed. How We Think About This Role IT is a product, not a ticket queue. We measure this function by whether a Stord employee can do their job on day one and every day after, not by SLA attainment on tickets that should never have existed. A well-run IT function makes most of its own tickets disappear. Sophisticated application of AI Before we add a person, buy a tool, or build an integration, the first question is whether an agent can do the work. You own making AI the normal way your own functions operate, and being the person who can tell a genuine agentic workflow from a thin wrapper around an API call if a vendor is selling you one. One system of record per domain. Customers, vendors, products, locations, employees. If a team is keeping a shadow spreadsheet, that is a defect in your architecture. Tool sprawl is a tax, and you are the person who collects it. Every SaaS application at Stord gets a named owner, a renewal date, a utilisation number, and a security posture. R&D will continue to decide the tools they need. You own everything after that decision, from the contract and the licence count to who has access and what happens at renewal. Bring the same rigor to a $200k observability contract as we bring to a $200k ERP module, and give Procurement a technical counterpart who knows what the contract is actually for. Build, buy, or cut, decided deliberately. We will support a build when the process is ours and nothing off the shelf fits it. We will not back a build that exists because a configuration was hard. We should cut as often as we build or buy. Process before automation. Automating a broken process buys you a faster broken process. We would rather you delete a step than script it. If you read that and disagreed with any of these, tell us when we talk. That is a better conversation than agreement. What You'll Own Enterprise systems and architecture   The strategy, architecture, and roadmap for Stord's business technology stack across CRM, ERP, HRIS, CLM, Procurement, and Customer Success platforms Integration and data-flow decisions between those systems, and the ownership model that keeps them from drifting apart again A documented architecture with named owners, prioritised by business impact and not by who asked loudest   Business process and master data   Governance for the domains that matter most: customers, vendors, products, locations, employees. Defined once and sourced once The standards and quality frameworks that make business data something the company can