Contact
Tell us what is actually going wrong
A symptom is more useful to us than a feature list. Describe what happens today, what it costs, and what you would want to happen instead. An engineer will read it and reply with a view.
- Who reads this
- An engineer on the team, not a sales queue.
- What we reply with
- Whether technology is the right lever here, and what we would do first if it is.
- If we are wrong for you
- We will say so, and usually point you at someone better suited. Check the patterns first
- Direct email
- hello@livingtech.in Write to us directly
Project enquiry
Describe the situation.
Fields marked * are required. The more concrete you are about the constraint, the more useful the reply.
Direct
Email us
For general enquiries, project discussions, or anything that does not suit a form.
hello@livingtech.in
Careers
Join the team
No vacancies are listed. We are always willing to meet strong engineers and problem solvers.
See careers
What makes a reply useful
Four things worth including
- The operational constraint, not just the feature
- Which systems are involved today
- Who owns the decision internally
- Any deadline that is genuinely fixed
Read first
If you are not sure where to start
- Solution patterns, the problems we recognise on sight
- Capabilities, how the work is actually delivered
- Industries, the closest match to your operating model
- Insights, our thinking before you talk to anyone
We do not publish a phone number or office address on this site. If you would rather speak, email first and we will arrange a time that suits you.