JONATHAN MALOY / SAAS TECHNOLOGY ADVISOR

I’ve built the systems.
And made the decisions.

I bring both perspectives to the table, so we can talk about the business problem and understand what solving it actually requires.

Jonathan Maloy
BUILDER. LEADER. TECHNICAL COUNTERPART.

Comfortable with
both sides of the work.

I’m a technology executive currently serving as CTO of a SaaS company in the construction and asset-management space. My work connects product and business priorities with the engineering systems that have to support them.

That includes architecture, engineering leadership, infrastructure, data, enterprise integrations, and security. Some days the work is a conversation about tradeoffs. Other days it’s understanding how a database, an authentication flow, or a production integration actually behaves.

That range matters. Advice is more useful when it accounts for the people who will implement it, the systems already in place, and the cost of changing them.

My work has included keeping payroll and billing rules separate, matching imported reference data without losing local decisions, and defining how an application session ends without disrupting a wider sign-in relationship. The details are different; the responsibility is the same: understand the business consequence before changing the system.

Explore selected work
WHY I WORK THIS WAY

You deserve a
clear explanation.

My advisory practice gives founders and engineering teams a way to bring in that experience for a defined decision, review, or working relationship. You may need an independent view of an agency proposal, a plan for an enterprise integration, or help choosing where AI belongs in the team’s work.

I help founders and teams ask better questions, make risks visible, and decide what deserves attention. Sometimes that means supporting an existing engineering lead. Sometimes it means being an independent technical representative in a conversation with a development agency or enterprise customer.

You work directly with me. We agree a specific engagement, a useful working rhythm, and the decisions or deliverables we’re working toward.

I continue to work as a SaaS CTO. Advisory availability and response expectations are agreed explicitly, so the engagement fits the work you need and the people who already own delivery.

See how we can work together
RELEVANT TECHNICAL GROUNDING

Depth where
it makes a difference.

My background spans operational SaaS products, asset management, logistics, work orders and maintenance, telematics, and large operational datasets.

Architecture & engineering

Laravel, PHP, relational databases, AWS, APIs, infrastructure, engineering leadership, and technical product discovery.

Enterprise systems

OAuth / OIDC, SSO, Microsoft Entra ID, SCIM, SAP-related architecture, data platforms, Databricks, and telematics integrations.

Security practices

Cloud and application security, vulnerability management, SDLC controls, customer security reviews, and engineering readiness for SOC-related requirements.

Leadership & AI adoption

Technical strategy, vendor evaluation, development oversight, due diligence, team leadership, AI-assisted development workflows, and the evaluation of practical automation opportunities.

WHAT THE TEAM CAN EXPECT

A recommendation
they can work with.

I explain the options and the reason for a recommendation. I make the next action and its owner clear. If the evidence is incomplete, that limitation belongs in the decision.

Your existing technical lead or development partner can carry the work forward. Where hands-on architecture or implementation would help, we can define that work separately.

See AI Enablement & Automation
A DIRECT CONVERSATION

Have a technology decision
you need to get right?

Tell me what’s happening. I’ll let you know whether I can help
and how I’d approach the next step.

Talk to Jonathan No sales team. You’ll talk directly with me.