Frequently Asked Questions
What kinds of businesses do you work with?
We focus on organizations where field execution and office reporting drift apart — mining and geology, power delivery and construction, and other field-heavy, data-heavy operations. That said, the underlying problem (systems that don't talk to each other) shows up everywhere, and we'll tell you honestly if your project is outside our sweet spot.
How does pricing work?
Most engagements are scoped as a fixed-fee project based on a written proposal, with milestone-based invoicing. Ongoing work (support, iteration, advisory) can be arranged as a retainer. We provide an estimate before any work begins — you'll never be billed for work you haven't approved.
Are you tied to a specific software platform?
No. We choose the platform that fits the problem — whether that's building on Microsoft 365/Azure (which many of our clients already own), open web technology, or another stack entirely. We'd rather point you to an existing product than build you something worse.
What does a typical engagement look like?
It starts with a discovery conversation to understand what's actually breaking down in your business. From there we send a written proposal with scope, timeline, and cost. Once approved, you get a dedicated project folder, a communication channel, and a live status view so you always know where things stand.
How do payments work?
Invoices are sent electronically with a secure payment link (card or US bank transfer via Stripe). International clients can pay via bank transfer through Wise. See our Payments page for details.
Do you sign NDAs / handle confidential data?
Yes. Confidentiality is standard in every engagement agreement, and we scope data access to only what's needed to do the work.
Who owns what you build?
You own your data and your deployment, always. Everything runs inside your own Microsoft tenant — I don't host your data and I don't hold it. You receive the solution files and the documentation, and you get a perpetual licence to keep using what I've built for you.
The underlying tooling I build with stays mine, the same way a carpenter owns his saw and the client owns the house. More on why I work this way.
What happens to my systems if we stop working together?
They keep running. Because everything lives in your tenant, nothing switches off when our engagement ends. Within thirty days I hand over the solution files, credentials, documentation and everything a successor would need — no conditions and no exit fee.
My access is delegated and you can revoke it in one click, at any time, without asking me.
You're one person. What's the risk to me?
A fair question, and worth answering plainly. Your systems run on Microsoft's infrastructure, not on me — so my availability doesn't determine whether your business operates tomorrow.
Beyond that: the documentation is written for a successor rather than as a reminder to myself, the solution files are already in your possession, and every configuration decision is recorded with the reasoning behind it. If I disappeared, another competent engineer could pick it up. That's a deliberate design goal, not an afterthought.
How do I get started?
Email justin@cronkcompanies.com with a short description of the problem you're trying to solve. We'll set up a time to talk it through.