Rosemont, IL — Greater Chicagoland
Contact Geek Engineering About an Engineering Project
Send the drawings, the control narrative, the software scope — or just the problem in plain words. A senior engineer reads every brief and answers it directly.
Geek Engineering can be contacted about an engineering project by describing the equipment, process, software or objective involved. A senior engineer reviews each brief and responds with a straight assessment of technical fit and what scoping the work properly would require. Confidential handling can be arranged before any sensitive material is transferred.
What happens next
Three steps, no sales queue
- A senior engineer reads itYour brief goes to the discipline lead it belongs to — controls, mechanical, or software — not into a sales queue.
- We ask the questions that change the scopeEquipment and process, site, timeline, constraints, and what “done” has to look like for you to sign it off.
- You get a written technical responseFeasibility, the approach we would take, the open questions, and the next concrete step.
Reach the engineering team directly
Call, email, or send the brief below. Requirements, mechanical schematics, and software scope all land with the same senior engineering staff who would run the work.
- The objective, and the equipment or process it involves
- Site location and the timeline you are working to
- Known constraints and any preferred platforms
- Drawings, programs, photos, manuals, or data you already have
Sensitive drawings or data can be discussed before you send anything across.
Project Brief Form
Tell us about your project — a senior engineer reviews every brief.
What to include, and why
Each of these changes the answer you get back, not just the length of it.
| Include | Why it changes the answer |
|---|---|
| The objective, in plain words | Determines whether the right service is even on this site |
| Equipment or process involved | Establishes discipline mix and whether onsite work is needed |
| Site location | Decides the delivery model and travel implications |
| Constraints that are genuinely fixed | Budget shape, downtime windows, platform standards, compliance |
| Target timeline and what drives it | A date tied to a shutdown differs from an aspirational one |
| Any documentation that exists | Drawings, program backups, photos, manuals, data — outdated ones still help |
| What you have already tried | Prevents repeating work and often locates the real constraint |
None of this needs to be complete. A brief with three of these is more useful than a polished document that arrives two weeks later.
Last reviewed by Geek Engineering senior engineering review.
Before you reach out: common questions
What is needed for an accurate engineering quote?
Four things: the current state of the equipment and controls (including documentation condition, honestly stated), the required functionality with clear boundaries, the acceptance criteria, and site constraints. With those, an experienced firm can quote with modest contingency; without them, every number contains guessing.
How should I prepare for an initial engineering consultation?
Share the business objective, equipment or process involved, site location, target timeline, known constraints, preferred platforms, and any available drawings, programs, photos, manuals, data, or requirements. Sensitive materials can be discussed before transfer.
How quickly will I hear back after submitting a project request?
A senior engineer reviews qualified project requests promptly during business hours. Including the equipment, objective, location, and timeline in your first message shortens the path to a useful technical response.