Customer and partner portals
Bring requests, documents, and agreed status information into a workspace with clear account permissions.
Explore the capabilityFor small & mid-sized businesses
Custom software and automation for growing businesses.
Custom software, workflow automation, and engineering support for growing businesses. Salt helps connect the applications and processes your team depends on without assuming every system needs replacing.
Relevant experience
Review the work behind the conversation.
The inventory portal and appraisal workflow projects show application and process work. Specific integrations and efficiency targets for your business need their own assessment.
Promotional products
MyPowerStock inventory portal
Salt developed MyPowerStock for Power Promotions: a custom inventory portal and sales enablement platform, with product engineering and CI/CD work included in the engagement.
Documented project scope
Explore the project - Custom inventory portal
- Sales enablement platform
Real-estate appraisal
Real-estate appraisal workflow automation
Salt delivered a product engineering engagement for JC Valuers and Advisors focused on business-process automation for a real-estate appraisal business.
Documented project scope
Explore the project - Business-process automation
- Real-estate appraisal business context
Where we can help
Choose the work
that matters now.
These are starting scopes. Your systems, decision owners, and delivery constraints shape the final proposal.
Document and workflow automation
Reduce repeated data entry by routing submissions through validation, exception handling, and human approval.
Explore the capabilityReporting your team can use
Connect agreed data sources and define the measures used to prioritize sales or operational follow-up.
Explore the capabilityExisting software improvements
Review a difficult application, integration, or release process and plan targeted changes around ongoing operations.
Explore the capabilityFrom discussion to delivery
A first engagement
with clear decisions.
- 01
Map the current process
Walk through one real example, including delays, exceptions, and who owns each step. Identify the source systems and the cost of the current workaround.
- 02
Scope a useful first release
Choose a workflow with a named business owner, representative test records, and measurable acceptance criteria. Confirm interfaces before promising automation.
- 03
Roll out with the team
Test with the people doing the work, agree data migration and fallback steps, and provide the documentation needed to operate the new workflow.
Delivery ownership
Choose how we work together.
A defined workflow project
A practical fit when the process and acceptance criteria can be agreed. The proposal sets out scope, milestones, dependencies, and change handling.
Discuss the right setupExtra engineering capacity
A fit when you already manage software delivery and need specific skills. If you need delivery coordination too, discuss a managed team.
Discuss the right setupWorking with your US team
Agree time-zone overlap, communication channels, decision-makers, repository access, and review cadence before delivery begins. Scope, staffing, commercial terms, ownership, and post-launch responsibilities belong in the proposal and agreement.
Before you begin
Questions to resolve
before committing.
You need a business owner who understands the workflow and can make decisions. The level of technical leadership and coordination Salt provides is agreed in the engagement scope.
We inspect the actual APIs, access permissions, identifiers, and data quality. Where an interface is limited, we discuss alternatives and the operational implications.
Yes. One request type, department, or data handoff can provide a useful first release. Define what success looks like before expanding the work.
Agree operating documentation, training, issue ownership, monitoring, and any ongoing support separately in the proposal. Support coverage should match how your business uses the application.
Start with a short brief
Discuss your business workflow.
Describe one manual process or disconnected system, who uses it, and what needs to improve. A few sentences about the current workflow are enough.