Business Systems
Choose a software firm for the work you need to change
Start with the assignment. A partner portal, an internal knowledge assistant, an ERP implementation, and a tool connecting existing applications require different evidence from a development firm.
- Published
- Author
- Demari Miller
- Series
- Cass & York
- Reading time
- 4 min read
Share this article
Start with the assignment. A partner portal, an internal knowledge assistant, an ERP implementation, and a tool connecting existing applications require different evidence from a development firm.
The providers below are worth investigating for those different needs. Compare their published work, then ask them to address the same transaction from your business.
Cass & York publishes this guide and provides software and integration services. Project descriptions come from the linked sources, checked on October 2, 2026; the fit judgments are our editorial interpretation.
Match the shortlist to your assignment
A service-coordination product for several types of users
- Firm and published evidence: Atomic Object's Bluepine project involved a household-management application, user testing, and transition to an internal team.
- Question to take into evaluation: Who will design and test the experience with your users, and who takes over after launch?
An internal assistant using scattered knowledge
- Firm and published evidence: thoughtbot's healthcare project addressed employees working with research and documentation, with UX, security, and onboarding work.
- Question to take into evaluation: Can the proposed team demonstrate your source-access rules and the actions your assistant will need?
A platform-based ERP covering core business functions
- Firm and published evidence: Itransition's footwear project used Odoo configuration and customization for ordering, product data, accounting, CRM, and a B2B website.
- Question to take into evaluation: Which requirements fit the platform, and which need custom work or separate systems?
Customer operations connected across existing applications
- Firm and published evidence: Cass & York's Vintel project covered portals, provisioning, Zoho CRM and Inventory synchronization, administrative controls, and monitoring.
- Question to take into evaluation: How will your specific corrections and failed updates be handled?
These are different project types, not interchangeable examples. The shortlist is organized by user experience, systems involved, delivery work, and ownership after launch. Use the category closest to your need, then request evidence for the remaining requirements.
A provider with a relevant product example may still need to demonstrate your accounting connection. A firm implementing an ERP should explain how it would preserve local applications if that is part of your assignment.
Use one brief with every serious candidate
Here is a fictional brief you could adapt:
“A contractor submits completion details and photos for two sites. Operations approves each site separately. Finance receives only approved billing information. The contractor then corrects one site's quantity after the other site has been approved. During the next update, the destination stops responding.”
Ask the firms to walk through the records, screens, and recovery. Who reviews the correction? Does the earlier approval survive? How will staff find out whether the destination accepted the update?
Our proposed design gives each site submission its own identity and review version. Approval applies to that version. A correction creates a new version for review and retains the earlier decision.
After a timeout, the item remains unresolved until the destination is checked or the same request is repeated using supported duplicate protection. The destination's actual interface determines what recovery is possible.
This is a proposed design to discuss with a firm, not an implemented demonstration. Ask each candidate to show its approach at the same level of detail.
Compare the proposal the team will actually deliver
Use the same questions and record the evidence beside each candidate.
- Team: Who interviews employees, makes design decisions, implements the connections, and remains involved at rollout?
- Workflow: Where do users submit, review, correct, and approve the item? What record shows each decision?
- First delivery: Which users, sources, screens, and actions are included? Which difficult cases will be tested?
- Estimate: Does it include source cleanup, integration access, training, deployment, and ongoing operation? What is excluded?
- Handover: What code, access, documentation, and support responsibilities will the buyer receive?
An unanswered question belongs in the next discussion. It does not establish that the firm cannot do the work.
Put prices beside equivalent work
A quote for screens alone cannot be compared directly with a quote that also includes data cleanup, integrations, and rollout. Ask the candidates to price the same initial assignment and identify dependencies.
Confirm the assigned team, current availability, commercial terms, and how later changes are approved. Published project pages cannot settle those details for your engagement.
Cass & York's published work covers connected applications and custom business tools. For the partner-submission example, a proposal starts with submitter, operations, and finance users tracing a representative item. The design sets out the review versions and destination exchange before delivery is priced.
Share this article