Contact

Contact Us — Case Study Help & Support

This site is static on purpose: fast pages, no accounts, nothing to leak. The practical result is that email is the way in. The form below assembles a clear message in your own email app — it sends nothing by itself — and the checklist shows what to include so the first reply can actually solve something.

1channel: email
0forms that store your data
1 daytypical reply window*

*Within one business day for most pre-order questions; see response expectations below.

The email builder

Fill in what you can, press the button, and your email app opens with the message already written: subject, topic, deadline and body sorted. You read it, add anything you like, and press send yourself. The page never transmits anything — there is no server here to receive it, and nothing you type into the fields leaves this tab until your own email app sends it. If your email app does not open automatically, the composed link appears underneath so you can tap it directly, and a copy button puts the whole message on your clipboard.

Contact form

Opens your email app — nothing is uploaded

Prefer to write directly? Copy the address

No form needed — the address below works in any email client. Copy it, write at your own pace, and use the checklist further down so the reply can be specific. Messages with a rubric attached get the most useful answers; messages with just "how much for a case study?" get questions back, which costs you a day.

[email protected]

Response-time expectations

Honest expectations beat optimistic ones, so here is how the channel works. Email is read on business days. Most pre-order questions get a reply within one business day; anything that needs a writer's opinion — subject coverage checks, unusual formats, dissertation stages — can take longer, because the alternative is a fast wrong answer. There is no live chat, no phone line and no 3 a.m. support desk; a site built on static pages keeps honest office hours.

What a good reply thread looks like, so you can steer it there: your first message describes the job, the reply either answers it or asks one clarifying question, and from there the thread stays short. If the answer needs scope, deadline and rubric details, the reply will say exactly which three things to send — reply with those and the conversation ends in an answer, not in another question. Keep the whole brief in one thread rather than scattering it across five emails; future-you will thank present-you when searching for the terms that were agreed.

Message typeBest channelWhat to expect
"Can you help with subject X by date Y?"Quote form on the order pageA scoped answer with delivery date — the fastest path to a real yes/no.
Pre-order questions, subject checksEmail via the builder aboveUsually within one business day.
Mistakes in a guide or toolEmail, topic "mistake to report"A thank-you either way; fixes land with a bumped "Last updated" date.
Privacy questionsEmail, topic "privacy question"A plain-English answer, referencing the privacy policy.

What to include for a fast, useful reply

The single biggest speed factor is what your first message contains. Tick through this list before pressing send — it is the same checklist the order walkthrough uses, trimmed for a first contact.

0 of 8 included
  • Your course level and module name
  • What the assignment is: case analysis, report, presentation, dissertation chapter
  • Word count or page count
  • Referencing style, if you know it (APA, MLA, Harvard, other)
  • Deadline with date, time and time zone
  • Whether you have a draft already, or nothing at all
  • The one question you most want answered
  • Anything you are unsure is allowed by your institution's rules — we would rather discuss it early
One privacy note: do not paste your university login, ID number or anything your institution would flag as sensitive. Nobody here needs it, and a good brief never requires it. The privacy policy explains what happens to everything you do send.

Frequently asked questions

Why is there no normal web form that sends from the site?+

Because this site runs on static hosting by design: no backend, no database, no message store. The builder composes the email, your email app sends it, and the message lives in your sent folder where you can always find it. The trade-off — no in-browser inbox — buys speed, privacy and a site that cannot leak what it never stored.

Can I attach my rubric and lecture slides?+

Yes, as attachments in your own email client after you send the first message — the builder's job is to get the conversation started with the right subject line and structure. Rubrics and assignment sheets are the two attachments that improve answers the most.

I need a quote urgently — is email still the right channel?+

For an urgent scoped order, the quote form is faster because it asks the structured questions (level, length, deadline) up front and routes your brief straight into the process. Email is better for context-heavy questions where you need a human to read the situation first.

Will you answer questions about the free tools too?+

Gladly. Bug reports, "how do I export my SWOT?" and "why does the counter say X?" are all fair game — pick the tools topic in the builder. Most tool questions are answered fastest by the tools themselves: they run entirely in your browser, so nothing you type ever reaches a server to go wrong.

Was this contact page easy to use?