Tripp Martin

Enterprise Software Architect

I design Dynamics 365, Power Platform, and public-sector procurement systems— backed by 25+ years of building and leading complex enterprise software.

About

I'm a software architect based in Greenville, SC specializing in eProcurement and ERP software. I enjoy taking complex requirements and building solutions that work.

With 25+ years of experience across the full software development lifecycle, from leading offshore teams and designing product enhancements to implementing complex ERP solutions, I thrive on turning requirements into reality.

When I'm not coding, you'll find me on a pickleball court, biking, or working on calisthenics.

Tripp Martin

Experience

Software Architect

CroweJan 2022 — PresentRemote
  • Led three public-sector Microsoft Dynamics 365 implementations from project start through go-live
  • Architect solutions across accounts payable, accounts receivable, asset management, procurement and sourcing, and warehouse management
  • Provide technical leadership within a flexible 5–6 person development team, contributing to architecture, delivery, code review, ALM, CI/CD, and release management

Key Accomplishments

  • Designed an X++ REST integration that lets users interact with OnBase content inside D365 instead of switching between systems
  • Migrated three ISV products to Git and redesigned their Azure DevOps pipelines and release processes to support the new workflow
  • Led adoption of Claude Code and Codex across our 5–6 person development team, improving delivery speed and code quality
X++D365 F&OAzurePower PlatformDataversePCFPower BISQL ServerAzure DevOpsGitREST APIsClaude Code

Software Development Lead / Manager

ProactisJan 2012 — Nov 2021
  • Led a 5–10 person offshore development team delivering customer enhancements for a large eProcurement platform
  • Translated customer requirements into technical designs, user stories, acceptance criteria, and product-roadmap priorities
  • Owned release management, build automation, technical debt, production escalation, and technical support for sales

Key Accomplishments

  • Transitioned the team from Waterfall to Agile and introduced a documented JIRA-based user-story workflow
  • Implemented WebProcure for three state governments, including complex ERP integrations
  • Modernized delivery and architecture through Jenkins deployment pipelines, Spring Boot services, external REST APIs, and migration of four products from Perforce to Git
JavaOracleSQL ServerJIRAHTMLJavaScriptXMLCSSJenkinsGitSpring BootREST APIsAgileMicroservicesPerforce

Software Developer / Development Lead

Commerce OneJun 1999 — Jan 2012
  • Designed and delivered customized Java-based eProcurement solutions for key enterprise clients
  • Led development delivery, coordinating with clients and QA to keep enhancements on time and aligned with requirements
  • Resolved complex production issues and delivered tested fixes, release packages, and customer installation guidance
JavaOracleSQL ServerJIRAHTMLJavaScriptXMLCSS

Selected Work

Representative architecture and delivery work, summarized without client-confidential details.

Enterprise integration

D365 and OnBase content workflow

Challenge
Users needed access to enterprise content while completing finance and operations work in D365.
Architecture
Designed an X++ REST integration that connects D365 Finance & Operations with OnBase ECM.
Outcome
Documents became available inside the D365 workflow, reducing the need to switch between systems.
X++D365 F&OREST APIsOnBase

Public-sector delivery

Government eProcurement implementations

Challenge
State governments required procurement workflows and ERP integrations tailored to public-sector operations.
Leadership
Led delivery, translated requirements into technical designs, and coordinated development and quality teams.
Outcome
Implemented the WebProcure platform for three state governments with complex ERP integrations.
JavaOracleERP IntegrationeProcurement

Platform modernization

Procurement delivery modernization

Challenge
A mature procurement platform needed more independent delivery, modern integrations, and repeatable releases.
Architecture
Introduced Spring Boot REST services, external APIs, Jenkins automation, and a documented Git workflow.
Outcome
Enabled independent service deployments and migrated four software packages from Perforce to Git.
Spring BootREST APIsJenkinsGit

Skills

Languages

X++JavaC#JavaScriptTypeScriptPython

Platforms & Frameworks

D365 F&OPower PlatformDataverseSpring BootPCF Controls.NET

Tools & Infrastructure

Azure DevOpsGitJenkinsDockerSQL ServerOraclePower BI

Practices

REST APIsMicroservicesCI/CDAgileALMIntegration Architecture

Contact

Feel free to reach out — I'm always open to new opportunities and conversations.