How Raxiwin scopes a new project in one week
A look at the discovery process Raxiwin uses before any code gets written, and why rushing this stage almost always costs more time later.
Thoughts on building software, working with clients, and running a small studio — straight from the people at Raxiwin.
A look at the discovery process Raxiwin uses before any code gets written, and why rushing this stage almost always costs more time later.
Why Raxiwin favors well-supported, proven technology over the newest framework for most client projects, and when it's worth breaking that rule.
Lessons Raxiwin learned building reporting tools for non-technical users, and the small design decisions that made the biggest difference.
Raxiwin's approach to estimating work without over- or under-charging clients, including how scope changes are handled mid-project.
Why Raxiwin believes most internal tools don't need a complex architecture to be genuinely useful to the people who rely on them daily.
Why Raxiwin isn't trying to grow into a large agency, and what the team believes gets lost when a studio scales too fast.
Send Raxiwin a note — client questions often turn into future blog posts.
Contact Raxiwin