James Allman / JA Technology Solutions LLC
How I Work
Whether your organization is a large enterprise or a focused operation with critical business systems, here is how I work, what to expect, and answers to the questions prospective clients ask most often.
Engagement Model
I specialize in ongoing support relationships, supplementing existing IT staff or providing expertise that organizations lack in-house. I also take on project-based work for migrations, integrations, reporting initiatives, and targeted technical problems.
Engagements range from a single phone consultation and fix to in-depth analysis of a business or software problem. I prioritize business-critical issues but otherwise schedule 30 to 45 days out depending on current workload.
All work is performed remotely. For each client, I use a dedicated virtual machine and connect through the client's approved secure access methods, including VPN where required. I work under least-privilege authority to protect both the client's environment and the integrity of the work.
Working with Your Team
When working with unfamiliar systems, I investigate the existing environment by analyzing its structure and data flows and work closely with subject matter experts who know the business context. I work directly with C-suite management, controllers, CFOs, CIOs, and business end users to understand requirements and design solutions that fit how the organization actually operates.
I can collaborate with an existing IT team, though I prefer to be solely responsible for the work I deliver. This ensures accountability and avoids the coordination overhead that slows down smaller engagements.
Direct Consultant Relationship
Working directly with me means the focus, accountability, and efficiency that larger teams often struggle to match. There is no handoff to junior staff, no coordination overhead, and no dilution of expertise. When you work with me, you are working with the person who understands your environment, makes the technical decisions, and delivers the result.
For larger projects that benefit from additional support — project management, specialized testing, documentation, or other complementary roles — I bring in trusted outside professionals who work under my direction and my umbrella. You still have a single point of accountability and a consistent relationship, with the flexibility to scale when the project warrants it.
What a Professional Consulting Engagement Provides
Working with an independent consultant is not the same as hiring a freelancer, a contractor, or an offshore outsourcing firm. A professional consulting engagement means business-level accountability, domain expertise that goes beyond the code, and a relationship that continues beyond the current project.
The difference matters most when the systems are business-critical — when downtime costs money, when data integrity is non-negotiable, and when the person doing the work needs to understand the business as well as the technology. I operate through a US-based business entity, maintain professional tools and environments, and bring 35 years of enterprise context to every engagement.
Offshore teams may offer lower rates, but they rarely bring the domain knowledge, regulatory awareness, or direct accountability that business-critical systems require. Your production data, compliance obligations, and institutional knowledge deserve someone who operates in your time zone, under your jurisdiction, and with a direct stake in the outcome.
A professional consultant understands your ERP, your compliance requirements, your reporting workflows, and the business consequences of every technical decision. That understanding is what protects you.
Ready from Day One
I maintain my own professional development environments, licensed tools, and specialized utilities across every platform I work on — IBM i, Linux, Windows, Java, .NET, database systems, and more. There is no procurement process, no license approval, no IT provisioning, and no budget request on your side.
When an engagement begins, I am ready to work immediately with the tools the job requires. Internal teams often face weeks of delay waiting for software approvals, license purchases, and environment setup. That friction does not exist when working with me.
This also means I stay current. My tools are always up to date because they are part of my professional practice, not a line item that gets deferred to next quarter's budget.
Pricing
I offer flexible engagement options: daily rates for ongoing work, hourly rates for well-defined requests, fixed-price project estimates for migrations, integrations, and reporting initiatives, and retainer agreements at reduced rates for ongoing support relationships.
Engagements range from a single phone consultation and fix to long-term support relationships. The scope and structure are determined by what the project needs, not by a one-size-fits-all model.
Rates reflect over 35 years of senior-level experience and the direct relationship — you work with me, not a team. An initial conversation is the best way to understand scope, discuss fit, and determine the right engagement structure.
Budgeting: Capital vs. Operating Expenditure
Consulting engagements may fall under capital expenditure or operating expenditure depending on the nature of the work. New application development, system migrations, and modernization projects that create lasting business assets are often capitalizable under accounting standards like ASC 350-40. Ongoing support, maintenance, troubleshooting, and routine enhancements are typically treated as operating expenses.
Many engagements involve both — an initial project phase that may be capitalizable followed by ongoing support that is operational. I can structure engagements to align with your organization's budgeting and approval process, whether that means separating project work from support, phasing deliverables across budget periods, or documenting scope in a way that supports your accounting team's classification.
Your accounting team determines the final treatment. What I bring is experience working with organizations where this distinction matters and the ability to structure the engagement so it fits your financial planning, not just your technical requirements.
Frequently Asked Questions
Do you work on-site or remotely?
Remotely. I connect over your VPN or other approved access method.
What does a typical engagement look like?
Anything from a single phone call and fix to an in-depth analysis of a business or software problem.
Can you work with our existing IT team?
Yes, though I prefer to be solely responsible for the work I deliver.
Do you support systems you did not originally build?
Yes. That is a core part of what I do.
How do you handle access to our systems?
Least-privilege authority, over your VPN, using a dedicated VM per client.
What industries do you work with?
Grocery retail, warehousing, and finance departments across varied industries.
How quickly can you start?
Business-critical issues are prioritized. Otherwise, 30 to 45 days out.
Do you offer ongoing support or just project-based work?
Both. Ongoing support is my specialty, but I also take on project-based work.
Do you provide source code for custom development?
For IBM i / RPG work, source code is provided by default. For other platforms, source code delivery is available as a separate agreement.