Custom software development

Business applications, workflow automation and internal systems. Work with CESAWS in Kolkata or remotely across India and internationally.

Custom software development illustration

How this could work for your team

A distributor wants sales to submit a priced order, finance to approve exceptions and fulfilment to see a single consolidated queue.

What we would check before launch

Run standard, incomplete and disputed orders against each role. Check whether reports reconcile with the record-level exports.

Custom software development features

Workflow and ownership mapping

Follow a request from creation through approval and completion. Record role changes, escalation, deadlines and exceptions such as a missing approver. A state diagram gives operations and engineering a common definition of what each status permits.

Business portals and dashboards

Give staff an actionable queue with filters for urgency, branch or assignment. Separate operational views from management reports so the totals answer a different question from the worklist. Define exactly when a record counts as complete.

Access controls and record history

Agree which roles may view, create, approve, export or reopen records. Include access restrictions for rows and attachments where required. Test the same record as an operator, manager and administrator before pilot rollout.

Existing data migration

Profile spreadsheets and current databases for missing identifiers and conflicting values. Agree matching rules and report rejected rows. Rehearse an import, reconcile totals against source reports and document how late changes enter the final migration.

Integrations with existing software

Decide which application is authoritative for each field and when another application receives an update. Define how users are informed if synchronization is delayed. Test repeated events and dependencies that may sometimes be unavailable.

Pilot and staged rollout

Select a department that can supply representative work and review the exceptions. Define a fallback during the pilot and compare work against the agreed success measures. Extend to other teams after the pilot feedback has been acted on.

Move work out of spreadsheets and into one system

When departments re-enter the same order in separate tools, small mismatches become difficult to trace and delays go unexplained.

Bring one workflow from start to finish, including a handoff, an exception and who can approve it. We use that example to define state transitions, audit data, permissions and the smallest release that removes useful manual work. Acceptance can include reconciliation between the reporting screen and the records behind it.

Typical project scope

  • Workflow approvals and exception handling
  • Customer and staff portals with role-based access
  • Reporting, exports and data migration
Scope a software project

What to prepare and what to expect

Bring a representative example

Share a representative order, its states, the exception rules and the people allowed to resolve each exception.

Agree on deliverables

Workflow map, access matrix, audit history, export and reporting.

Plan handover

Give the operations owner a tested way to correct records and verify changes without bypassing approvals.

Example brief for a dispatch system

A small manufacturer records shipment approval in messages and delivery changes in spreadsheets. The first release brings requests, approver decisions and delivery exceptions into one queue. Test a rejected shipment, a partial dispatch and a cancelled order, and compare the management report to the existing ledger before automating the next stage.

Discuss this project with CESAWS

Questions before you enquire

Can an existing spreadsheet become our system?

It can be an input. We review the data, separate source records from calculated values and agree which cleanup the business must perform.

What determines the scope and timeline?

Share a representative order, its states, the exception rules and the people allowed to resolve each exception. We confirm the first release, dependencies and review schedule in the proposal.

What to bring to the first call

Share a representative order, its states, the exception rules and the people allowed to resolve each exception.

What we will confirm together

Give the operations owner a tested way to correct records and verify changes without bypassing approvals.

Scope a software project

Questions about scope and cost

Can we keep the current database?

Review its schema, support requirements, access model and data quality first. If reuse meets the application's needs, build a compatible cutover plan with backups and rehearsal.

How should we choose the first release?

Choose a complete workflow with a clear owner and frequent use. Include the most expensive exception early so the pilot exercises the real decision process.

Can we scope this for your business?

Share the workflow or site you want to improve, your deadline and who needs to approve the project.

Scope a software project