Home/Contact
Start with the problem,
not the brief.
Describe what breaks today and who it hurts. A person replies within one business day, and the first conversation is free — nobody quotes anything until we have both seen the same thing.
IST (UTC+5:30) · Sunday closed
Start here
The form is the brief.
Pick what this is about and the checklist above the message box changes to match. The more of it you can answer, the more useful the first reply is.
Before you write it
The same enquiry, twice.
Both are shapes of message a contact form produces. One of them costs you a day, because the only honest reply is four questions. Illustrative examples, not real enquiries.
Hi, we need a website for our company. Can you also share pricing and your portfolio? Thanks.
- No current state, so we cannot tell what exists today.
- No systems named, so we cannot judge integration risk.
- No scale, so any number we give is a guess.
- No date, so we cannot say whether we are free.
We are a 40-person distributor in Ahmedabad. Quotations are built in a spreadsheet and re-keyed into our ERP, so a pricing error reaches a customer about twice a month. We want one place where a salesperson builds a quote, someone approves it, and it lands in the ERP without re-keying. On-premise ERP, around 12 users, 3,000 SKUs. It should be live before the next financial year. Budget is agreed internally, but I would rather hear your range first.
- What breaks today, and how often.
- The systems it has to talk to.
- Scale: users, records, transactions.
- The date that actually matters.
- Where the money conversation starts.
Handling
Five fields, one inbox, no third parties.
The form on this page is a small piece of production Laravel rather than a hosted widget, so here is the whole path your message takes and what the server accepts.
Nothing on this page is validated in JavaScript, because there is no JavaScript on this page.
The field contract
| Field | Type | Required | Limit |
|---|---|---|---|
| name | string | required | 100 characters |
| email address | required | 255 characters | |
| phone | string | optional | 20 characters |
| subject | one of six | required | 200 characters |
| message | text | required | 2,000 characters |
| _token | CSRF token | required | same-origin |
The maxlength on each input is the same number, so the browser stops you before the round trip and the server checks it again regardless. Five submissions a minute per address, then the throttle turns you away rather than we do.
The next two weeks
What sending this actually starts.
Four steps, none of which is a drip campaign. Nothing here is a commitment until day five, when the quote stops moving.
A person replies.
Your message is written into our own system and emailed to the team. Whoever would run the work answers with either the questions we still need, or a time to talk.
The consultation.
About an hour, with the people who will use the thing rather than only the people paying for it. If we are not the right people you hear it here, not in month three.
Discovery, if you want it.
Only once you say go. Requirements ranked, a stakeholder map, a technical approach and the three risks most likely to bite — written down rather than presented.
Fixed timeline, fixed quote.
With the names of the people who will be on your pod. Nothing here is a range that quietly widens later.
Still deciding
Questions about writing to us.
Scope, ownership and stack are answered on the services page. These are the ones about this page. If yours is not here, it makes a good first line for the form.
Or skip all of it
contact@scorptechsolutions.com
Both reach the same inbox and the same people as the form.
How quickly does someone actually reply?
Within one business day, Monday to Friday. Something sent on Friday evening is answered Monday. The form is not monitored out of hours, so anything genuinely urgent should go to the phone number rather than here.
We do not have a spec yet. Is it too early to write?
No, and a spec written before anyone has seen the system tends to be the expensive kind. Most projects start as a description of what breaks. Discovery exists precisely to turn that into a scope on one page.
What will it cost?
There is no price list because there is no standard project. You get a range on the first call, once we know the systems and roughly the scale. The number that stops moving is the fixed quote at the end of discovery, and we would rather give you that late than give you a guess early. The three engagement models are compared on the services page.
How long will it take?
Nobody can answer that honestly from a contact form. What you can have inside the first week is a scope on one page with the timeline attached to it, and from there every sprint ships to a real staging URL, so you watch progress rather than wait for it.
We already have a codebase and a developer. Do you still work with us?
Yes. Day two of week one is access and audit: repository, hosting, analytics and domain reviewed, and the existing system walked end to end. Read-only access is enough to start. We would rather inherit something honestly than replace it reflexively.
Something you built for us is broken.
Choose Support as the subject and include the URL, what changed just before it started, and whether it is blocking work right now. If it is already a project we run, raising it in the client portal lands it against your project instead of in a general inbox.
You are in Ahmedabad. We are not.
We work with clients across India and abroad. Office hours are IST (UTC+5:30), the working rhythm is async by default, and calls get scheduled where the two days overlap rather than where ours is convenient.
What happens to what I send?
It is stored in our own database and emailed to the team, and it is used to reply to you. It does not go on a mailing list, and there is no third-party form service anywhere in the path — the diagram above is the whole of it.
Have a difficult problem?
Let’s turn it into a product worth building.
Free consultation · reply in one business day · +91 91733 99077