Let's talk
Every successful product starts with the right conversation
Whether you are validating an idea, modernising an existing platform or looking for strategic technology leadership, let's explore the possibilities together.
- Based in
- Mumbai, India
- Response time
- Within two working days, personally
- Availability
- A small number of engagements from September 2026
- Working with clients in
- India, the United Kingdom and the United States
- Preferred first step
- A short written summary, then a 30-minute call
Before anything is scoped
Clarity before commitment
The first conversation is not a pitch. It is a working session to establish whether there is a real problem worth solving, and whether I am the right person to solve it with you.
How the first conversation works
You describe the business situation in your own language. I ask questions until the problem is stated precisely enough to be solved, and I say plainly where I think the risk sits.
By the end you should have something useful whether or not we work together: a clearer problem statement, a view on sequence, and an honest read on cost and complexity.
The business problem
What outcome is blocked, and what it costs to leave it as it is.
Current challenges
Where the process, platform or team is straining under real usage.
Desired outcomes
What good looks like in commercial terms, not feature terms.
Technology landscape
What already exists, what must be kept, and what is negotiable.
Expected timelines
Which dates are fixed by customers, funding, audits or regulation.
Engagement enquiry
Tell me about the work
These questions exist so the first reply is substantive rather than a request for more information.
What happens next
From enquiry to kickoff
Five steps, each with a defined output. Nothing moves forward until the previous step is genuinely settled.
- 01
Initial Review
I read your enquiry myself and form a view on whether the problem is one I can genuinely help with.
Within two working days
- 02
Discovery Conversation
A 30-minute call to test the problem definition, the constraints and the outcome you are aiming for.
30 minutes
- 03
Technology & Product Assessment
A written read on architecture, delivery risk, security and compliance implications of the direction you are considering.
Same week
- 04
Proposed Engagement Model
A defined scope, sequence and commercial shape — advisory, build, or fractional leadership — with what is out of scope stated plainly.
One page
- 05
Project Kickoff
Access, environments, decision owners and the first reviewable increment agreed before work begins.
On agreement
Who should reach out
Where this work fits
The common thread is a business decision with technology consequences, not a request for hands on a keyboard.
Founders
Pre-build decisions where architecture and scope determine whether the runway is enough.
Business Owners
Manual operations that have become the ceiling on growth.
Private Equity Portfolio Companies
A credible technology plan and delivery accountability post-investment.
Growing Enterprises
Platform consolidation, integration and internal systems that scale with headcount.
Healthcare Organisations
Clinical and quality workflows where evidence and auditability are designed in.
Financial Services
Controlled environments where access, records and supplier assurance are scrutinised.
Product Teams
Discovery, architecture review and AI feature design alongside an existing team.
Technology Leaders
A senior second opinion on decisions that are expensive to reverse.
What to expect
How the conversation will feel
Professional, specific and free of the usual sales apparatus.
Thoughtful discussion
Questions about the business before questions about the stack.
Honest recommendations
Including when the answer is a smaller build, a different tool, or no build at all.
No sales pressure
No follow-up sequences. If it is not a fit, I will say so and point you elsewhere.
Practical technology advice
Specific to your constraints, usable whether or not we work together.
Business-first thinking
Decisions justified in cost, risk and time to value.
Clear next steps
You will always know what happens next and who owns it.
Direct channels
Or reach me directly
Every channel reaches me personally. No intake queue and no assistant triage.
Best for anything with context to share. Include the outcome, the constraint and any fixed dates.
diasjordan@gmail.comPhone
Best for a quick read on fit or timing. Mumbai, India, so calls are scheduled to overlap with your working day.
+91-800-710-5544Useful if you would rather establish context first, or review professional background before a longer message.
Connect on LinkedInStay updated
Occasional notes, not a newsletter cadence
A short email when there is something genuinely worth reading. No sequences, and unsubscribing takes one click.
Topics covered
- Technology Strategy
- AI Product Development
- Privacy & Compliance
- Product Thinking
Mention “stay updated” in your enquiry or email and I will add you. A standalone sign-up is being set up.
Questions
Before you write
Answers to what most people ask first.
- What happens after I submit an enquiry?
- I review it personally and reply within two working days with a direct read on the approach I would take and whether I am the right person for the work. If it looks like a fit, the next step is a 30-minute discovery conversation to test the problem definition — not a sales presentation.
- Is the first conversation chargeable?
- No. The initial review and the discovery conversation are free. Paid work begins only once a scope, sequence and engagement model are agreed in writing.
- What should I include in the project description?
- The outcome you are trying to reach, the constraint currently blocking it, any deadline that is fixed by customers, funding, audits or regulation, and whether an existing team or system is in place. Two paragraphs is usually enough.
- Do you work with businesses that already have an engineering team?
- Yes. A significant part of my work is fractional technology leadership alongside an in-house team: setting architecture direction, raising delivery standards and owning the decisions that are expensive to reverse.
- Which regions and time zones do you work across?
- Clients in India, the United Kingdom and the United States. Calls are scheduled to overlap with your working day, and written updates carry the detail so nothing depends on a single meeting.
- How is my information handled?
- Enquiry details are read by me only, used solely to respond to your enquiry, and never shared, sold or added to a marketing list.
Credibility
Reserved for published material
These surfaces will hold attributed client statements, talks, interviews and publications. Nothing is placed here until it is real and cleared for publication.
Testimonials
Attributed client statements, published with permission.
Client Feedback
Outcome notes from completed engagements.
Speaking Engagements
Conference and industry sessions on AI delivery and governance.
Interviews
Long-form conversations on technology strategy.
Publications
External articles and contributed pieces.
Awards
Recognition for delivered work.