Contact · Wages.software
One address. A person reads it. There is no form on this site.
Everything reaches [email protected]. There is no contact form on any page of this site, no lead capture, no cookie and no tracking pixel — the marketing server is stateless by design, uses no third-party advertising or tracking scripts, and builds no behavioral profile, so a message you send lives in a mailbox rather than in a lead system attached to a product you have not bought. Basic short-lived operational logs may record page requests.
It is a small thing to design around, and it is the same posture as the rest of the product: if a surface does not need to keep something, it should not be able to.
What gets answered, and how
Five kinds of question, and what a useful reply needs.
Same address for all of them. The difference is what to put in the message so the first reply is an answer rather than a request for more detail.
Early access
Which of the three uses is yours — verifying a provider’s figures, calling one calculation from a system you already run, or satisfying a control an auditor asked about — and roughly the size of the payroll you are thinking about. One paragraph is plenty.
A technical question about an engine
Name the surface and, if you can, the behaviour you expect. The engines are described by module and by function on the engines page, so a question can be as specific as “what does the basis do when two exemption windows overlap” and get a specific answer back.
“Is this actually built?”
The best possible version of this question names the capability. Eleven modules are written with no production caller and they are listed by name, so in most cases you can answer it before we do — and if the answer there is ambiguous, that is a defect on our side and worth telling us about.
Privacy, data and security review
Say which wall you are asking about: the tenant wall, the fail-closed finance-role gate, the deny-by-default self lane, or the masking of bank details. Each is a different mechanism and the honest answer differs for each. Payroll and HR carry no student identity.
Press, or a correction
If something on this site is wrong, that is the message we most want. Every claim here is meant to be checkable, and a claim that turns out not to be gets corrected on the page rather than quietly softened.
What happens after you write
A reply from a person, and no sequence.
Writing to the address above does not enrol you in anything. There is no drip sequence, no nurture track, no scoring, and no second email that arrives because you did not answer the first — those all require a system holding a record of you, and this site does not create one.
What you get is a reply from somebody who can answer the question. If the honest answer is that a capability you need is one of the eleven modules with no production caller, the reply says that, and it is usually shorter than a call would have been. If the honest answer is that a full-service provider is a better fit for what you described, the reply says that too. Both of those are worth more to you than a scheduled demo, and they cost us less.
If it turns into a conversation, the conversation is a walkthrough of what is wired and what is not, against the surfaces themselves. The test we hold ourselves to is that you should leave able to repeat back which is which. A call after which you could not is a call that went wrong, whatever else happened in it.
What we will not do is put a date on something unbuilt to keep a conversation going. If a module has no production caller today, we will tell you it does not and we will not name a quarter. A date given to close a call is the kind of claim that is impossible to correct later without it looking like a retreat.
What we will not answer
Three questions where the honest reply is that we do not know.
How another provider computes internally. We cannot read another company’s source, so any answer would be a guess pointing in the direction that flatters us. An earlier version of our own comparison table asserted two things about a competitor’s internals; we could not source either, and both are gone. We will describe our own behaviour precisely and say “not established” about theirs.
Whether a particular withholding treatment is correct for your jurisdiction. That is a question for whoever signs your tax tables. This product is deliberately built so that the person who signs is a person and not us: the registry ships empty, an unsigned table withholds zero, and we invent no rate.
When something unbuilt will ship. If a module has no production caller today, we will tell you that it does not and we will not put a quarter on it. A date given to close a call is the kind of claim that is impossible to correct later.
If you are an employee, not a buyer
We are not who you need, and here is why that is the right answer.
People sometimes reach a page like this looking for their own pay stub, their W-2, or a change to their direct deposit. If that is you, this is the wrong address, and the reason is worth a paragraph rather than a redirect.
We hold nothing about you. Wages.software is software a school or business office buys; we are not your employer’s payroll department and we do not operate a payroll on anyone’s behalf. There is no account here to look you up in. The employee self-service lane in the product is built and walled — own row only, deny by default, the employee reference resolved from the session rather than taken from a request — and it reads pay tables that nothing in production writes, so even inside a school running this, it returns an honest empty result today.
And we could not help you if we wanted to. Writing to us with a Social Security number, a bank routing or account number, or a tax identifier would put sensitive data in a mailbox for no benefit — we would not be able to act on it and we would rather never receive it. Please do not send any of those. Your employer’s business office or HR department is the correct route for every one of those requests, and they are the only party who can act on them.
The one thing we can say that might be useful: those fields are treated as hard-sensitive throughout this product. Bank account numbers are returned masked to the last four digits and never echoed in full, and in the grounding wall written for a future payroll assistant, Social Security numbers, routing and account numbers, direct-deposit details and tax identifiers are never admitted to the grounding set at all — not for an employee, and not for an HR administrator.
What this page does not do
No form, cookie, checkout, or scheduling widget.
This page holds an email address and nothing else, and that is the complete list of what it does. There is no form to submit, so there is no field to validate, no record created and nothing to leak. There is no cookie set anywhere on this site. This page loads no third-party advertising, tracking, chat, analytics, or calendar script. Basic short-lived operational logs may record page requests.
There is also no live checkout and no price. Money is switched off end to end: no charge rail for buying this and no disbursement rail inside it. A pricing page for a product you cannot buy implies that you can, so there is not one.
If you would rather read than write, the fastest honest picture of what this is comes from two pages: the engines that are wired, and the eleven modules that are not. Between them they are most of what a call would cover.
Where to go next
The rest of this site.
Every page here is its own argument rather than a restatement of the home page. If you would rather ask a person, the address below reaches one.