Contributor guidelines
Write for StackQuarry.
We consider original practitioner analysis that helps mid-market buying committees understand the consequences of a software decision.
What makes a useful contribution
A strong submission begins with a decision faced by IT, finance or FP&A, procurement, or a functional operator. It shows the implementation, adoption, commercial, or switching consequences behind a software category. Concrete definitions, formulas, bounded examples, checklists, and failure modes are welcome when their assumptions are clear.
We do not consider generic thought leadership, disguised product promotion, fabricated evidence, scraped or lightly rewritten work, unsupported superlatives, or articles written primarily to place a link. Submissions should be original and should disclose relevant vendor relationships or conflicts.
How to submit
Email contact@stackquarry.com with a short summary of the decision, intended reader, proposed outline, and why you can address it responsibly. Send the draft only as a Google Docs link or a direct DOCX, Markdown, HTML, or PDF attachment. Do not send arbitrary download links, archives, macros, credentials, or confidential company data.
Editorial review
Acceptance is not guaranteed. We may edit for clarity, evidence boundaries, accessibility, and house style, or decline material that does not serve the reader. Publication timing, placement, and links remain editorial decisions. Submission does not create an employment, advisory, or continuing publication relationship.