The Idaho Stack
Tracking Idaho’s technology economy

Send us something specific

Submit a tip, company, field note, correction, or interview idea.

A good submission includes a place, a system, a person who can explain it, and something we can verify: a document, source link, photo, quote, public record, job post, meeting agenda, or firsthand example.

Company map

Submit a company

Name, city, category, source link, and why it matters in Idaho. We use this to improve the company map v0.

Open →

Field notes

Send a field note

One specific moment from your work, what it revealed, and what outsiders miss. Short is fine.

Open →

Interviews

Suggest an interview

Tell us who they are, what system they understand, and why Idaho readers should hear from them.

Open →

Corrections

Send a correction

Point us to the exact page, sentence, and source that shows what needs to change.

Open →

The Constraint

Pitch a constraint

Where does the process slow down? Water, power, labor, software, permitting, repair, broadband, or something else.

Open →

Watchlist

Send an event or job lead

Workforce programs, public meetings, hiring waves, grant deadlines, and technical events belong on our watchlist.

Open →

Good submissions

  • Founder or operator notes
  • AI experiments inside Idaho businesses
  • Repair, hardware, field-tech, or infrastructure lessons
  • Agtech, broadband, energy, or workforce observations
  • Student, educator, researcher, or technician perspectives

Formats

  • 150–300 word field note
  • 5-question Q&A interview
  • Contributed article or commentary
  • Anonymous background tip for research

Editorial promise

Contributions may be lightly edited for clarity, length, and factual precision. We do not fabricate quotes. Contributors can review their own quotes or field notes before publication. Promotional submissions may be labeled or declined. Corrections are welcome.

What helps most

Send evidence, not polish.

The strongest submission is not a perfect essay. It is a specific Idaho example with something verifiable: a source link, meeting agenda, public document, job posting, photo, quote, invoice range, outage pattern, delayed part, equipment bottleneck, or named person who can explain the issue.

If the subject involves a company or public agency, say what stage the claim is in: announced, funded, permitted, hiring, operating, delayed, cancelled, or disputed. That helps us avoid turning hopes into facts.