Contact — since 2014

Let's build something remarkable, together.

Every inquiry reaches me personally. No queues. No gatekeepers. No pressure. Tell me what you have in mind, and I'll reply within one business day with honest guidance — whether or not we end up working together.

Currently accepting new projects

II.

Tell me about the project.

Share as much or as little as you like — a few sentences is plenty.

Please complete the highlighted fields.

Your details will be used only to reply. No lists. No spam.

Message received.

Thank you for reaching out. I'll reply personally within one business day. In the meantime, feel free to email or call directly.

III.

Answers to questions most clients ask.

01 How much will my project cost?

It depends on scope, complexity, and timeline — no website or app carries a single "price." After a short discovery call I send a written proposal with a fixed price and deliverables, so there are no surprise invoices. Small projects start in the low hundreds; full applications run into the thousands or tens of thousands. Every budget is considered.

02 How long does a project take?

A simple marketing site: 1–2 weeks. Full multi-page sites with custom features: 3–6 weeks. Mobile apps and business applications: 6–16 weeks depending on complexity. Every proposal includes a realistic timeline, and I flag slipping dates early — surprises at the end are the worst part of software work.

03 Do you work with remote clients?

Yes — most clients are remote. Video calls for discovery and review, email or Slack for day-to-day, a staging link you can share with anyone. Based in Chicago (Central Time), working coast to coast and overseas.

04 Who owns the code and the work?

You do, in full, once the project is paid for. No vendor lock-in. No licensing traps. You receive the source code, the designs, and documentation to hand to another developer if you ever need to. NDAs signed on request.

05 Can you take over an existing website or app?

Yes. Inherited projects are a specialty. I take the time to understand what's there before changing anything, write down what I find, and either stabilize or modernize the work depending on what you need. Rescue engagements often begin with a paid audit so you know exactly what you're working with.

06 Do you offer ongoing support after launch?

Yes. Every project includes a launch-support window — typically thirty days — to catch anything that slipped through. Afterward, you can reserve monthly hours for ongoing work, or return ad-hoc whenever a need arises. No forced retainers.

07 What do you need from me to get started?

Honestly, very little. A short description of what you want and why is enough to book a discovery call. No need for a finished brief, wireframes, or technical specs — figuring those out is my job. Bring examples of things you admire, rough thoughts, and any hard constraints. We go from there.

One last invitation

Still reading? Let's talk.

The easiest projects to say yes to begin with a conversation. Pick whichever way is easiest for you.

Daniel Cywinski