[Contact—]
Let's talk about your project.
Two ways in. The 30-minute call below is the fastest; we'll book inside the week. The form further down is for when you'd rather write the problem out first, and I'll reply personally within a couple of business days.
Based in Kitsap County, WA · Pacific Time
(360) 850-7876 · calls and texts both fine during Pacific business hours
Fastest path
Grab 30 minutes on my calendar
No prep, no obligation. I'll listen, ask the right questions, and tell you honestly whether your project fits what I do.
· or send a written brief ·
Brief builder
Have something in mind but not sure how to ask?
Copy the prompt below into ChatGPT, Claude, or any chat AI. It will ask you a few questions about your problem, your setup, and what success looks like, then write a structured brief you can paste into the form.
I want to hire a software developer (Penumbra Tech, penumbra-tech.com) for a project, but I'm not sure how to describe what I need. Please help me put together a structured project brief by asking me one question at a time. Cover these topics in order: 1. What's the actual problem or opportunity? What's broken, slow, or impossible right now, or what would you like to be true that isn't? 2. What's your current setup? Tools, vendors, and software you already use (Shopify, Wix, QuickBooks, spreadsheets, custom code, etc.). 3. What have you already tried or considered? 4. What does success look like in concrete terms? More bookings per week, hours of admin saved, a new revenue stream, fewer support tickets, etc. 5. Budget range and timeline. "Not sure" or "exploring" is a valid answer. 6. Tell me about your business: size, industry, and what your customers care about. After I've answered, write up a brief with these headings: - Context (who I am and what we do) - Problem (the actual pain in plain language) - Current workaround (how I'm dealing with it today) - Desired outcome (what success looks like, with numbers if I gave you any) - Constraints (budget range, timeline, team size, anything else) - Open questions (anything you think the developer would want to know that I didn't cover) Keep the brief under 400 words. Don't invent details I didn't give you. Don't pitch solutions, that's the developer's job after they read the brief. Just clearly capture what I told you.