How to brief a software project so the estimate means something
Ten things to put on one page before you ask for a quote, and how to read the proposals that come back.
Plain-language notes from our work: how to brief a project so the estimate means something, whether a static site or a CMS fits, how to decide what to build, what a bilingual site needs, how to prepare for an internal system, and how we keep our free study sites accurate.
Ten things to put on one page before you ask for a quote, and how to read the proposals that come back.
The choice is about who will change the site, how often, and who keeps it safe. Five questions, a comparison, and what we would pick for each kind of site.
Most businesses should buy, not build. Here is how to tell when you are the exception, and what to ask before you commit either way.
A language toggle is the easy part. These are the things that decide whether Chinese-speaking customers in Canada actually find and trust your site.
Orders, inventory, scheduling, HR: an internal system can put all of it in one place. The projects that go well settle these ten things before anyone writes code.
A practice question that teaches the wrong answer is worse than no question. These are the rules our driving-test and citizenship-test sites are built on.