Your quotation wasn't rejected. It went to spam.

You priced it properly. You sent it the same afternoon. You followed up on Sunday and again on Wednesday.

Nothing. Two weeks later you hear the job went to someone else, and you conclude you were too expensive.

Possibly. But there is a duller explanation that accounts for a large share of these, and it is worth ruling out before you start discounting: the procurement officer never saw the mail. It was filtered on arrival, into a folder nobody in a busy facilities office opens.

Why a corporate mail server distrusts your message

Every incoming mail is scored before delivery. The score asks one central question: can this message be proven to come from where it says it comes from? Three DNS records answer it, and most small contractors in the Gulf and India have none of them configured.

SPF — which servers are allowed to send as you

SPF is a published list of the mail servers permitted to send on behalf of your domain. Without it, a receiving server has no way to distinguish your genuine mail from anyone forging your address. Unverifiable mail scores badly, and a PDF attachment with a price in it scores worse.

DKIM — a signature proving the message wasn't altered

DKIM attaches a cryptographic signature to each outgoing message. The receiving server checks it against a key published in your DNS. If it matches, the message is intact and authentically yours. If there is no key to check against, there is nothing to verify.

DMARC — what to do when the first two fail

DMARC ties SPF and DKIM together and tells receiving servers how to treat mail that fails them. Absent a DMARC record, each provider applies its own defaults — and for an unauthenticated domain sending attachments to a corporate tenant, those defaults are not generous.

None of this is exotic. It is three text records in your DNS, configured once, and it is the difference between your mail being scored as verified business correspondence and scored as an unknown.

The Gmail problem, stated plainly

A large number of working contractors quote from companyname@gmail.com. It is free, it works, and everyone at the company already knows the password.

Two things follow from it, and only one is technical.

The technical one: you cannot authenticate a domain you do not control. Gmail's own infrastructure is well-configured, so the mail usually arrives. What you lose is everything downstream of the address — you cannot add colleagues under the same domain, you cannot recover the account if the person who created it leaves, and you cannot build a sending reputation that belongs to your business rather than to a consumer mailbox.

The commercial one matters more. A procurement officer comparing three quotations for the same scope reads the sender address as a proxy for how established the company is. Two arrive from a company domain. One arrives from Gmail. Nobody writes this down as a scoring criterion, and it influences the decision anyway — particularly on a first engagement where they have nothing else to judge you by.

What separates a delivered quotation from a filtered one

Filtered	Delivered
Sent from a free consumer mailbox	Sent from your own domain
No SPF record published	SPF published, listing your actual sender
No DKIM signing	DKIM key published and signing enabled
No DMARC policy	DMARC published, monitoring at minimum
Subject line: "Quotation"	Subject: enquiry reference, site, scope, date
Price only inside a 9 MB attachment	Scope and price summarised in the body; attachment supports it
No website; domain resolves to nothing	Domain serves a live site over HTTPS
Follow-up as a fresh mail each time	Follow-up in the same thread

Two of those are not about authentication at all. A price that exists only inside a large attachment gives the recipient nothing to act on if the attachment is stripped, and a fresh mail on every follow-up removes the thread history that makes a conversation look legitimate.

What it costs to fix

Less than most contractors assume, which is the part that tends to be surprising.

For Sky Rope Technical Services in the UAE, a client who approved these figures for publication, annual domain and hosting came down from ₹5,175 to ₹528 — an 89.8% reduction — on a rebuild that also included branded email on their own domain with no per-mailbox subscription fee, and an integrated CRM. At today's rate that is roughly AED 199 down to AED 20 a year.

That figure is one client's and it will not be identical for everyone — it depends on what you are currently paying and what the rebuild involves. The structural point holds regardless: the annual cost of a properly configured domain, branded email and a live site is small enough that a single lost quotation almost certainly exceeds it.

How to check yours in ten minutes

1. Send a test mail from your business address to a colleague on a corporate tenant — a client contact you trust, not another Gmail account. Ask them to check the spam folder, not just the inbox.
2. Run your domain through a public SPF, DKIM and DMARC lookup. Note which of the three come back missing.
3. Open your own website on mobile data with the browser bar visible. If a security warning appears, that domain is damaging you in two places at once.
4. Check whether anyone can currently send mail appearing to come from your domain. An open domain is a spoofing risk, not only a delivery one.
5. If you quote from a free mailbox, register the domain first. That single step is a prerequisite for everything else on this list.
6. Publish SPF, enable DKIM signing, and add a DMARC record in monitoring mode. Move to a stricter policy once you can see that legitimate mail is passing.
7. Rewrite your standard quotation subject line to carry the reference, site and date — so it is findable later, by them.

What this doesn't fix

Authentication gets the mail delivered. It does not make the price competitive, and it will not win a job you were never going to win. If you are consistently losing on rate, this is not your problem and you should stop looking here.

It also does not help where the client uses a procurement portal. Increasingly in the Gulf, larger facilities and developers route quotations through a system rather than email, and getting registered on it is a separate exercise with its own requirements.

And no configuration overcomes a message that reads like a template. Delivery is a prerequisite, not a substitute for a quotation that answers what was asked.

What it does is remove a failure mode you currently cannot see. Every other lost job gives you feedback of some kind. This one gives you silence, and silence is the thing that gets misread as a pricing problem.