448 N La Salle Dr, Chicago
Contact LaunchPad Lab
Tell us what you're building, or what isn't working. The project inquiry form goes to our team and we reply by email or phone, usually within one business day. If you'd rather skip the form, the address, phone, and email below reach the same people.
Direct lines
Phone and email reach the same team
Use the phone number or email listed here to reach the team directly. For project inquiries, the form below is usually fastest because it captures enough context for us to give you a useful first reply rather than a scheduling back-and-forth. LaunchPad Lab works on web, mobile, software, and AI development for US businesses, and the first reply comes from someone who would actually work on the project.
Chicago, IL 60654
United States Visits by appointment
What to include in your inquiry
The more context you give, the more useful our first response will be. A few lines about the product and the people who use it save a full round of questions later.
- What the product or system should do Scope
- Who uses it, and on what Users
- Whether any code exists today Starting point
- Any deadline you are working toward Timing
- A rough budget range, if you have one Approach
A budget range changes which approach we would recommend, which is why we ask. If you don't have all of this, send what you have. We'll ask the rest.
One business day for weekday inquiries
Messages sent over the weekend or on US holidays are answered on the next working day. If your project has a hard deadline, say so in the inquiry and we'll factor it into the first reply.
From there, a short scoping call covers the problem, the constraints, and a realistic first release. We tell you early if the fit isn't right.
Send a project inquiry
Your inquiry reaches our team and gets read by someone who'd work on the project, not a sales queue. The fields below cover what we need for a useful first reply. Everything else can wait for the call.
- Send what you have; missing details can be answered later.
- New builds and existing codebases both start here.
- Privacy questions can also go through the form; our Privacy Policy explains what it collects.
Prefer to talk first? Call +1 415-526-3479 during business hours, Monday–Friday, 9:00 AM – 6:00 PM.
New projects and existing codebases
We take on new builds and work on existing systems that need rework, modernization, or a cloud migration. If you're inheriting a codebase or dealing with a product that's become hard to change, describe the symptom rather than the diagnosis.
Slow builds, frequent outages, and features that take longer each release all point to different causes, and we'd rather find the right one before quoting work. Tell us what you are seeing and when it started; that is usually enough for the first call.
Rework and modernization
Inherited systems are common in our inbox. Bring the repository access question up early if you have it, and mention which parts of the product you would keep exactly as they are — the boundary between keep and rebuild shapes the plan more than any single technology choice.
See what we buildAsking about AI features specifically?
Mention the use case and what data the feature would need access to. Common requests are a copilot inside an existing product, chat search over internal documents, or automation for a document-heavy workflow.
During scoping we will tell you whether AI is the right tool for the job. Sometimes it isn't, and a plain search or rules-based workflow gets you a better result for less.
Finding the office in River North
We're in Chicago's River North area, on the ninth floor of 448 N La Salle Dr. Visits are by appointment, so let us know when you'd like to come by and we'll confirm a time.
Chicago, IL 60654
United States
Monday–Friday, 9:00 AM – 6:00 PM
+1 415-526-3479The building sits one block off the Chicago River, within walking distance of the Merchandise Mart and the Grand CTA station.
Questions that come up before people write
How quickly will someone answer?
Inquiries submitted on weekdays usually get a reply the same day or the next business day. Messages sent over the weekend or on US holidays are answered on the next working day. If your project has a hard deadline, say so in the inquiry and we'll factor it into the first reply.
Who reads my inquiry?
Someone who would work on the project, not a sales queue. That is why we ask for project detail rather than a call-scheduling link — the reply you get answers your actual question, and the first call can start at scope instead of introductions.
Can you work with a codebase we already have?
Yes. Existing systems that need rework, modernization, or a cloud migration are a normal part of our work. Describe the symptom rather than the diagnosis: slow builds, frequent outages, and releases that take longer each time each point to different causes, and the inquiry is where that conversation starts.
What if we don't know exactly what we want yet?
Send what you have. Choosing "Not sure yet" in the form is a real answer — scoping works best when the first call covers the problem, the constraints, and a realistic first release rather than a fixed feature list.
Where do I ask a privacy question?
Use the phone number or email on this page, or the contact details in our Privacy Policy. That page also explains what the inquiry form collects and why, so you can check it before you send anything.
Other ways to reach us
If the form isn't convenient, use the phone number or email on this page. For privacy questions or requests about personal data, use the contact details in our Privacy Policy, which also explains what information the inquiry form collects and why.