Introduction
How we can help
Whether you need a product demo, a scoped proposal for custom work, or advice on architecture and integrations, we read every message and reply with a practical next step.
We do not use a website contact form. Email and phone go directly to the team that scopes and delivers work, no ticket queues, no chatbots, and no automatic marketing follow-ups.
Include context: what you operate today, which systems you use, timeline, budget band if you have one, and constraints (compliance, uptime windows, languages). Plain language is fine. We translate technical detail on our side.
We typically respond within two business days. For urgent production issues, say so in the subject line and we prioritise accordingly. For NDAs before sharing architecture, ask in your first message.
After the first reply, we may suggest a short call, a product demo, or a fixed scope discovery phase depending on complexity. We do not send generic brochures or add you to mailing lists without consent.
Response
What to expect
2 days
Reply target
Most enquiries answered within two business days.
1 thread
Same team
No handoffs to anonymous inboxes.
Free
Initial scoping
First conversation to understand fit, no obligation.
Global
Remote delivery
Projects across time zones with async updates.
Reach us
Email and phone
We do not use a web form. Email and phone go straight to the team that ships the work.
Best for detailed requirements, attachments, architecture diagrams, and async follow-up across time zones.
Include in your message
- Company name, sites or regions, and your role
- Product line or service area you are asking about
- Timeline and any hard deadlines (launch, audit, season)
- Attachments welcome: brief specs, exports, or architecture sketches
Phone
Call when you need a quick steer on fit, timeline, or which product line matches your operation. If we miss you, leave a message. We call back within two business days.
Good to mention
- Best number and timezone for a callback
- One-sentence summary of the problem or opportunity
- Whether you are evaluating build, buy, or extend an existing Vintorr product
Topics
Common reasons to reach out
Every enquiry is read by a human. We do not route you through anonymous inboxes or marketing automation.
Product questions
Demos, licensing, deployment options, and configuration for Vintorr product lines, from a single site pilot to multiple location roll-outs.
- Which product fits your operation
- Multi-site and integration options
- Pilot and rollout planning
Custom development
Applications, integrations, automation, and platform work with written scope and phased delivery you can fund incrementally.
- Discovery and fixed scope proposals
- Phased roadmaps for large programmes
- Rescue or refactor of existing systems
Partnerships
Resellers, integrators, and technology partners. Tell us how you work with clients and what joint delivery would look like.
- White-label or joint delivery models
- Referral and implementation partners
- API and integration partnerships
Careers
Open roles and general applications. Attach a CV and a short introduction on what you want to build next.
- Software engineering and product roles
- Fully remote · worldwide hiring
- Portfolio or GitHub links welcome
FAQ
Before you write
Do you work with clients outside Sri Lanka?
Yes. Vintorr is a fully remote company. We deliver across time zones with async updates and scheduled video calls. Engagements combine written scoping with live workshops when discovery requires them.
Can you start with a product and add custom work later?
Often yes. Teams deploy a Vintorr product line first, then extend it with integrations, custom modules, or adjacent workflows once operators are live on the baseline. The same team maintains both catalog and custom work.
What happens after the first email?
We reply with clarifying questions or a suggested call. If there is a fit, we outline discovery, a phased proposal, or a product demo. We do not send generic brochures. If we are not the right fit, we say so early.
Do you sign NDAs before discussing our systems?
Yes. Ask in your first message if you need an NDA before sharing architecture, data samples, or vendor contracts under review.