Talk to us about your data
A paragraph about your problem is enough to start. We reply from a real inbox, not a ticket queue.
Your email app should now be open
Press send there to reach us. We can’t confirm delivery from here, only that your mail app opened.
- Message drafted for info@imrsnt.com
Prefer to do it yourself? Write to info@imrsnt.com directly.
Nothing opened, or you closed it by mistake? Go back to the form. Your answers are still there.
What happens after you write
No forms to fill in after this one, and no sales sequence.
-
1
A person reads it
Every message is read by someone on the team.
-
2
A first conversation
We set up a call to understand the problem, the systems behind it and who needs the answer.
-
3
A written proposal
You get what we would do, in what order and what it would take, before any work starts.
Questions people ask first
If yours is not here, ask it in the form above.
How does an engagement usually start?
With a conversation about the problem, then a short discovery: we look at the systems and reports involved and come back with what we would do first, and why.
Do you work with the tools we already have?
Yes. We work in the platform you already run, whether that is SQL Server, Azure, AWS or a mix, and only suggest moving when there is a clear reason to.
Do you work on site or remotely?
Both. Our teams are in Johannesburg, Pretoria and Cape Town, and most work is a mix of on-site days for workshops and remote days for building.
How do you handle our data?
Under your access rules and on your systems wherever possible. We agree what we can see before we start, and nothing leaves your environment without your say-so.
Can you add engineers to our team instead of running a project?
Yes. We place data and software engineers inside your own team for as long as the work needs them. How embedded engineers work.
What does it cost?
That depends on the scope. After a first conversation you get a written proposal with the scope and the cost, before anything starts.