One senior engineer, accountable end to end.
Ingot Solutions exists because the gap in the market is not more developers. It is being able to talk to the person who will actually build the thing.
Most software consultancies are structured so that the people who sell the work are not the people who do it. You meet a principal in the pitch, sign with an account manager, and the code gets written by whoever was available — often several time zones and one abstraction layer away from the conversation where the requirements were agreed.
That structure exists for good reasons on large programmes. On the kind of work most organizations actually need — an internal tool, an integration, an automation that removes a recurring manual step, a cloud architecture that is currently one person's undocumented knowledge — it adds cost, latency and a translation error at every handoff.
What Ingot Solutions is
A senior-led consultancy run out of Calgary, Alberta, working with clients across Canada. The engineer on the first call is the engineer who designs the architecture, writes the code, runs the deployment and answers the phone when something needs attention two years later.
The practical consequence is scope discipline. A one-person firm cannot absorb a project that should never have been started, so the incentive runs towards getting the approach right at the start rather than billing through a wrong one. Several engagements have ended up notably smaller than what was originally asked for, because a sharper approach solved the actual problem with less.
Where the products come from
Clarivise Scan and Clarivise Shield are Ingot Solutions products, built and operated in-house. They exist partly as businesses in their own right and partly because running your own product in production is the fastest way to stop having theoretical opinions about licensing, managed deployment, cost control, incident response and what happens when a platform vendor changes their DOM.
Client work benefits directly from that. The key-custody pattern, the local-fast-path cost control, and the packaged enterprise deployment path all came out of shipping products, not out of reading about them.
The name
An ingot is refined material — processed, standardized, and ready to be made into something. It is not the finished object and does not pretend to be. That is roughly the right description of good engineering work for a client: solid, honest about what it is, and genuinely theirs to build on.
What gets used, and why it is a short list.
Depth beats breadth. Everything here is something used on delivered, production work — not a list of things once read about. If your problem needs something outside it, that is worth saying on the first call.
Languages
- TypeScript
- JavaScript
- Python
- C#
- PowerShell
- SQL
Front end
- React
- Astro
- SharePoint Framework
- Office.js
- Manifest V3 extensions
Back end
- Node.js
- FastAPI
- Azure Functions
- .NET
- PostgreSQL
- REST APIs
Cloud & platform
- Azure Static Web Apps
- Azure Container Apps
- Entra ID
- Microsoft Graph
- Microsoft 365
- Microsoft Purview
- Power BI
- GitHub Actions
AI
- Claude / Anthropic API
- Model Context Protocol
- Retrieval over document stores
- Structured output pipelines
Quality
- Playwright
- Unit testing
- CI pipelines
- Accessibility review
Worth a conversation?
If any of this sounds like the kind of help you need, the next step is a short call with no preparation required on your side.