1. 00.Start here

    commonbinary is an independent software product studio building configurable, purpose-built tools for modern businesses.

    We turn complex technical challenges into intuitive, reliable products. Our philosophy is simple: software should adapt to the business, not the other way around.

  2. 01.Software should fit the business

    Every business has its own people, processes, and challenges. Good software starts by understanding how they work and adapts as their needs change.

  3. 02.Make the complex feel simple

    The work behind a product can be complicated. The experience of using it shouldn’t have to be. We make clarity a design requirement.

  4. 03.Useful in everyday work

    Software earns its place when people can complete a task with less effort and fewer mistakes. We focus on the work a team does every day, not just the feature list.

  5. 04.Enterprise automation

    Reduce repeated data entry and manual handoffs. For example, an approved request could move to the right team with the information they need to act.

  6. 05.Developer infrastructure

    Give development teams tools and systems that make it easier to build, deploy, and maintain software reliably.

  7. 06.Data intelligence

    Bring information from different sources together so people can understand what is happening and make decisions with confidence.

  8. 07.Operational software

    Give teams a clearer way to manage the work behind their business, from tracking requests to coordinating tasks and approvals.

  9. 08.Configurable by design

    Teams work differently. Settings such as approval limits, roles, and notifications should be adjustable as a business changes.

  10. 09.Every feature needs a purpose

    A feature should solve a problem someone actually has. We start with the outcome, then decide what the product needs to do.

  11. 10.Reliability builds trust

    People need to know that their work has been saved, that a process has finished, and what to do if something goes wrong.

  12. 11.An independent studio

    commonbinary is an independent software product studio focused on building practical, purpose-built tools for businesses.

  13. 12.Follow the work

    A request might pass through a form, a spreadsheet, and several inboxes. Following it from beginning to end helps reveal where people are waiting or repeating work.

  14. 13.Understand the workarounds

    A spreadsheet may contain checks and decisions that exist nowhere else. Before replacing it, learn why people use it and what would happen if those checks disappeared.

  15. 14.Measure the repeated work

    A task that takes five minutes can consume hours when it is repeated throughout the week. Frequency and effort help identify where a change will matter.

  16. 15.Choose who to help first

    A person assigning work and a manager reviewing results need different information. Starting with one clear task helps make the first version useful.

  17. 16.Use familiar language

    Use the words a team already uses for its work. Familiar labels make software easier to learn and reduce ambiguity when people discuss a task.

  18. 17.Be clear about completion

    An invoice can be drafted, approved, sent, or paid. A useful status makes clear what has happened and what needs to happen next.

  19. 18.Automate the handoff

    When a quote is approved, its details can become the starting point for an order. Passing information forward reduces the need to enter it twice.

  20. 19.Handle the unexpected

    If an order arrives incomplete, a team needs to record what was received, explain the difference, and keep track of what remains. The workflow should accommodate that.

  21. 20.Make approvals clear

    Before approving a request, people should be able to see what is changing, who requested it, and the information needed to make a decision.

  22. 21.Test a rule before applying it

    Before changing how requests are assigned, preview the rule using past requests. This helps the team understand its effects before the change takes effect.

  23. 22.Show what is holding work up

    A request waiting for a signature needs different attention from one waiting for stock. A useful queue makes the reason for the wait clear.

  24. 23.Make repeat actions safe

    If a connection drops after an order is submitted, someone may click again. The system should help prevent an accidental duplicate.

  25. 24.Connect systems one step at a time

    Start an integration with one useful exchange of information. This helps uncover differences in required fields and formats before expanding the connection.

  26. 25.Help developers get started

    Clear documentation should show developers how to make a request, understand the response, and handle common errors.

  27. 26.Plan for changes to integrations

    When a system changes a field used by another application, teams need time and guidance to update the connection without interrupting their work.

  28. 27.Test without affecting real work

    Teams need a safe way to test a workflow from beginning to end without creating a real order, sending an unintended message, or changing live records.

  29. 28.Explain what went wrong

    If an import fails, identify the problem and explain how to correct it. A clear error can help someone finish the task without starting over.

  30. 29.Follow a request through systems

    A request can move through several services before it is complete. A shared identifier helps teams find where it is and investigate if it stops.

  31. 30.Agree on what a number means

    Sales and finance may count an order at different points. A report should explain how its measures are defined so people can interpret them consistently.

  32. 31.Make the source of a number clear

    When a total changes, people need to understand why. Where possible, let them trace a summary back to the records behind it.

  33. 32.Show when data was updated

    A stock count from yesterday may be less useful than one from five minutes ago. Show when information was last updated so people can judge how to use it.

  34. 33.Keep unknown information clear

    An empty delivery date means the date is unknown. Filling it with a default can make a report look complete while giving a misleading picture.

  35. 34.Compare like periods

    A partial month next to a full month can make demand look lower than it is. Use comparable periods and label results that are still in progress.

  36. 35.Support a clear handover

    At a change of shift, the next person needs to know what is open, what has already happened, and what needs attention. A useful handover brings that context together.

  37. 36.Make responsibility visible

    A shared queue should make it clear who is responsible for the next action and allow work to be reassigned when plans change.

  38. 37.Keep the reason with the change

    A revised delivery date is easier to understand when the reason is recorded alongside it. The next person can explain the change without searching through messages.

  39. 38.Make corrections straightforward

    Mistakes happen. People should be able to correct a record and understand what changed and why.

  40. 39.Design for the working environment

    Someone using a scanner in a busy warehouse has different needs from someone at a desk. The layout and controls should suit the conditions in which they are used.

  41. 40.Start with useful defaults

    A team should be able to complete its first task without configuring every setting. Defaults can provide a starting point while leaving room for change.

  42. 41.Give people appropriate access

    People should have the information they need for their work. Access can be tailored so sensitive records are limited to those who need them.

  43. 42.Make data portable

    Teams should be able to export their records in a useful format, with clear column names and identifiers that make the data easier to use elsewhere.

  44. 43.Check whether it helped

    After a change, ask the people doing the work to complete the task again. Their experience helps identify what improved and what still needs attention.