About Jim
I help organizations regain control of the technology they depend on.
I am a senior technology leader and architect with more than 30 years of experience across architecture, infrastructure, cybersecurity, cloud, web platforms, Drupal, vendor guidance, and hands-on delivery.
Working directly with me
The relationship is personal. The proof should be the work.
- Selected work written as situation, what I did, and result
- Architecture and platform decisions explained in plain English
- Articles with a visible point of view on ownership, open source, infrastructure, and modernization
- Project artifacts such as screenshots, diagrams, metrics, and before-and-after costs when they are available and safe to publish
How I think
I don't start by selling you a platform.
Before replacing anything, I want to understand why it is there, what it is costing you, who is responsible for it, what is actually broken, and what happens if we leave it alone.
Sometimes the answer is a rebuild. Sometimes it is moving away from a vendor. Sometimes it is tightening security, documenting ownership, or cleaning up hosting before anyone touches the application.
And sometimes the smartest advice I can give you is not to touch it yet.
Working principles
The useful answer depends on ownership, cost, risk, and maintainability.
-
01
Control matters
Your business should understand who owns the systems, data, access, documentation, and decisions it depends on. Outsourcing work is fine. Outsourcing all control usually is not.
-
02
Complexity has to earn its place
A simpler system people can operate is often better than an impressive system nobody understands. Architecture should make the next decision easier, not harder.
-
03
Vendors need daylight
Good vendors are valuable. Bad vendor dependency gets expensive quietly. I help separate useful outside help from lock-in, opacity, and avoidable spend.
-
04
Risk should be visible
Security, hosting, backup, data, staffing, and platform risks are easier to handle when someone names them clearly before they become emergencies.
Open source and commercial tools
Fit beats ideology.
Open source can preserve choice, portability, transparency, and long-term flexibility. Commercial platforms can be the right answer when they reduce real operational burden.
The decision should come from the business model, security requirements, internal capacity, budget, data ownership, and support reality. I care less about the label and more about whether the organization can understand, operate, and evolve the system after the decision is made.
What to expect
Senior involvement without the theater.
- Direct access to Jim
- Plain-English recommendations
- Hands-on technical depth when needed
- Vendor and platform independence
- Documentation and ownership clarity
- Practical advice even when the answer is to leave something alone