Idea Studio & Ventures · Case study
Whatif.buildTurning an open-ended idea into a first sentence someone will actually send.
- Client
- Whatif.build
- Industry
- Idea Studio & Ventures
- Market
- Calgary, Alberta
- Launched
- 2026
- Published
- Live site
- whatifbuild.com
- Status
- Content serves at whatifbuild.com; the site's canonical domain, whatif.build, showed a 'coming soon' page at the time of writing.
Overview
Whatif.build is a Christian idea-to-reality studio: a visitor finishes the sentence 'What if…', and a person — not a pipeline — reads it and replies with what it would take to make the idea real. Local Cochrane Web Design built whatifbuild.com as a single-purpose site whose entire job is to make that first sentence easy to write and send.
The design problem is unusual because the product is not a service with a scope; it is an invitation to say something half-formed. So the page removes every reason not to. The headline asks the question, a large single-line field is already prefixed with 'What if' and cycles through example endings, the helper text says 'You don't have to know how. Just the sentence.', and the only other fields are a name and an email. Below the form, a short three-stage path — Conviction, Pathway, Reality — explains what happens after, and one worked example shows an idea that was sent and acted on. The site is deliberately small; its measure is whether a visitor types.
The live site
Built to be judged in the only place that counts.
Captured from the live site — different pages, real pixels, no mockups.
The client
The studio's register is faith-rooted and direct — its footer reads 'This company powered by faith in Jesus Christ' — and its examples are civic and ministry ideas rather than products: a city-wide worship night, mentors for every teenager, a building nobody wanted becoming a home.
At the time of writing it carried one published case study, the OCT 31 Calgary worship night, presented as a question that was asked, the requirements it created, and outcomes the page itself marks as pending until the event has happened.
The challenge
An idea-submission site competes with the visitor's own hesitation. If the page asks for a plan, a budget or a category, the person with the half-formed idea — the one the studio exists for — closes the tab.
The studio also had almost no proof to show: one example, not yet complete. The page had to make the process credible on the strength of its clarity and its single honest example, without inflating either.
Strategic objectives
What the build had to accomplish.
Make the idea field the page: one line, already begun, with examples that show how little is required.
Ask for nothing beyond the sentence, a name and an email, and say what happens next and roughly when.
Explain the path from question to reality in three plain stages.
Show one real example with its outcomes marked pending rather than invented.
Keep the site fast and light enough that the form is interactive before the visitor has finished reading the headline.
The insights that shaped the work
The product is the sentence. Every element that is not the sentence is either helping the visitor write it or getting in the way.
'A person reads this — not a pipeline' is the only credential a studio like this needs on its first page, and it has to be true.
An example with pending outcomes, stated as pending, is more persuasive than a finished example that was never asked.
Chapter
A field that has already started the sentence
Insight
A blank text area asks the visitor to begin. Most people with an idea they are unsure of will not.
Decision
The form's single large input is prefixed with 'What if' in the studio's italic serif, and its placeholder cycles through endings — 'we filled a stadium to pray…', 'every teenager here had a mentor…', 'the building nobody wanted became a home…', 'the tool I keep sketching actually existed…', 'this town had one more reason to stay…' — so the visitor sees the shape of an acceptable answer before typing. The hidden label reads 'Your idea — finish the sentence'; the helper line beneath says 'You don't have to know how. Just the sentence.' Name and email follow, the button says 'Build this', and the validation messages stay in the same voice: 'Finish the sentence — we'll take it from there.' A draft is kept in the browser's session so a visitor who navigates away does not lose the line.
Effect
The threshold for sending drops to a single clause. The studio receives ideas in the form it wants them — a question, not a brief — from the people least likely to have filled in a conventional form.
Chapter
What happens next, said once and plainly
Insight
A visitor who sends an idea to a stranger wants to know who reads it and when they will hear back.
Decision
Beside the button the page states 'A person reads this — not a pipeline.' On submission the confirmation reads 'Received, [first name]' and 'Check your inbox — a copy of your question is already there.', and the page promises 'Usually within one business day you'll hear what we think it would take to make this real.' Below, the path is three stages with one word each — Conviction, Pathway, Reality — and a line that resolves them: 'And then it won't be a question anymore.' If sending fails, the message offers a direct email address instead of a retry loop.
Effect
The visitor knows the idea reaches a person, that they will get a copy, and roughly when a reply comes. The studio's whole process fits in the space between the headline and the footer.
Chapter
One example, with its outcomes left honest
Insight
A studio that turns ideas into reality needs to show it has done so. At launch it had one idea in progress and no finished results.
Decision
The 'What happened?' route presents a single case study as the site's own form would: the question that was asked — 'What if we organized a Calgary-wide worship night on October 31?' — then the requirements it created ('A room big enough', 'Churches in one room', 'An identity', 'Production', 'Reach', 'Funding and logistics'), photographs captioned 'We started here.', 'The venue, still a question.' and 'Hours before doors.', and an outcomes block whose only figures are '1 night planned' and '1 city'. The items still to come are listed as pending: 'Verified attendance and participating-church counts', 'Photography and film from the night', 'Named credits for volunteers, churches and production partners'. The credit line reads 'Concept and build — Whatif.build' with full credits 'to be confirmed with the organising team'.
Effect
The example demonstrates the method — question, requirements, work — without claiming an outcome the calendar had not yet delivered. A visitor sees that their own idea would be treated the same way.
Recognize your own business in this problem? The same system builds yours.
The mobile experience
An idea arrives on a phone, usually in the moment someone has it. The headline and the pre-started field fit the first screen, the cycling examples run in the field itself rather than above it, and the keyboard opens straight into the sentence. Name, email and 'Build this' follow in a single column, the three-stage path reads as three short rows, and the decorative canvas effects used on desktop are the first thing the page gives up on a small or slow device.
Colour & type
The palette below is sampled from the live Whatif.build site — the exact tones the brand is built on.
#1A1A19
#2A2A28
#6B6A68
#858482
#E0DEDA
#F2F0EC
Search & discoverability
This is a single-page application whose homepage ships as a shell and renders in the browser; the headline, form and path are not in the raw HTML, and the interior routes have no static fallback, so a direct link to the case study returns a 404 on the host while the client-side route works from the homepage. The page carries a title, description and social-card tags, and the application writes its structured data at runtime. Those limits are recorded here, and in the notes for the owner, rather than described as something they are not. What the site is built to be found for is a single question, and a single page can carry that.
Technology & ownership
The site is a small React application with a Supabase-backed idea submission that stores each idea and sends two emails — one to the studio, one to the sender — through a transactional service, with a direct email fallback in the error state. Three.js and smooth scrolling provide the desktop's visual effects as an optional layer; the self-hosted typeface and a minimal bundle keep the form interactive quickly. The idea draft persists in session storage so an interrupted visit does not cost the visitor the sentence.
Immediate outcomes at launch
The page's one action is a pre-started sentence with cycling examples, a name and an email — nothing else is required.
'A person reads this — not a pipeline.' and a one-business-day reply expectation are stated beside the button.
The process is published as three plain stages: Conviction, Pathway, Reality.
One case study is shown with its question, requirements and photographs, and its outcomes marked pending rather than invented.
Submissions are stored and acknowledged by email, with a direct address offered if sending fails.
Common questions
What owners ask before commissioning a build like this one.
How does a website help a visitor begin with an incomplete idea?
By starting the sentence for them. Whatif.build's single field is prefixed with 'What if', cycles through example endings so the visitor sees how little is needed, and says 'You don't have to know how. Just the sentence.' A name and an email are the only other fields.
What should an idea-submission page say about what happens next?
Who reads it, and when. Whatif.build states 'A person reads this — not a pipeline.', confirms receipt with the sender's name and a copy by email, and promises a reply on what it would take 'usually within one business day'. The process is three stages: Conviction, Pathway, Reality.
How can a new studio show examples before it has results?
By showing the method and marking the outcomes pending. Whatif.build's one case study presents the question asked, the requirements it created and photographs of the work, with its only figures being '1 night planned' and '1 city', and the attendance, photography and credits listed as still to come.
What are the known limits of this site?
It is a single-page application without prerendered HTML, so its headline and form are not in the raw response, direct links to interior routes return a 404 on the host, and its canonical domain currently shows a 'coming soon' page. Those are recorded as owner items in this study rather than described away.
What results does this case study claim?
None that were not observed. No submission counts, ideas realised or outcomes appear here, because none have been measured and the site's own example is dated after this writing. What is documented is the build — its form, its process copy, its example and its limits — verified against the live site and the studio's repository on 21 October 2026.
Where it stands
Whatif.build exists to receive questions people have not finished asking. Its website is the question, pre-started, with the fewest possible reasons to leave it blank. Whether the ideas become real is the studio's work; the site's work is done the moment someone types.
- Web Design
- Idea Submission Flow
- Brand & Narrative
More case studies
The same system, a different market.
Your project
Your business may have outgrown its website.
Whatif.build needed more than a redesign — it needed its real-world strengths made visible online. If that sounds familiar, tell us about your business. A written, itemised proposal comes back within one business day.
Free · No obligation · Written quote within 24 hours
Building Websites That Work as Hard as You Do