Contact
A Rough Description Beats a Polished Brief
Many people wait until they have a specification before writing to a developer. It is rarely worth the wait. Tell us how things work now and where they go wrong, and we can start from there.
Describe the Problem Here
Plain language is fine. The service dropdown only sorts the first read, so pick the nearest line and let the description do the explaining.
Without the form
Email Works Just as Well as the Form
Whichever route you take, the enquiry ends up as an email. To write from your own inbox, or to attach a document, use the address below.
Zevora Enterprise
MSME Registered Micro Enterprise
Phone
Address
Udyam no.
UDYAM-GJ-03-0846975
After you write
Questions Arrive Before Any Quotation
This is the order of events, not a schedule. No reply time is promised here.
Read in full
A person reads the whole message. Nothing automated answers on our behalf.
Questions go back first
Gaps in the description come back to you as specific questions by email. A price at this stage would be a guess, so none is offered.
A plain answer on fit
If the work is outside what we do, the reply says so rather than stretching to cover it.
A written outline if it fits
The approach, the scope as we understood it and the sensible next move, set out so you can check our reading of the problem.
An enquiry exists only as an email in our inbox. It is not copied into a database or any other system, and it is used for replying to you and nothing more. The Privacy Policy has the full terms.