Reply Smart

Software development

Software that fits the way your operation actually works.

We build new applications, rebuild the ones that no longer keep up, and migrate the ones that have to move — for finance, operations, manufacturing, and service teams. Always integrated with the systems you already run.

  • New build
  • Rebuild & modernization
  • Migration
  • SAP · Dynamics 365 · APIs

Illustrative delivery board

Delivery board · this sprint3 lanes · 6 items

New build

  • Operator app · shift handover

    In test
  • Service portal · installed base

    Build

Rebuild

  • Finance approvals · legacy form

    Cut-over planned
  • Planning tool · UI + API layer

    Build

Migration

  • Reporting DB → cloud

    Data validated
  • File interface → OData

    Parallel run
  1. CI/CD
  2. Build
  3. Tests
  4. Security scan
  5. Deploy staging

Three ways we take on software

New build, rebuild, or migration — each with its own rules.

The wrong approach is expensive in both directions: rebuilding what only needed a migration, or patching what really needed a rebuild. We say which one fits before we quote.

01

New build

When no standard product fits the process, or the process is your competitive edge.

What we do

  • Discovery with the people who will use it
  • Clickable prototype before real build
  • Backend, API, web and mobile front-ends
  • Integrations designed in from day one

What you get

  • A working first version in production early
  • Documentation and a maintainable codebase
  • A team that knows the process, not just the code
02

Rebuild & modernization

When an application still does the job, but nobody dares to change it anymore.

What we do

  • Map what the current system really does
  • Refactor, re-platform, or replace per module
  • New UI on a stable backend where that is enough
  • Parallel running and staged cut-over

What you get

  • Business continuity during the change
  • Clear rollback paths at every step
  • A platform you can keep improving
03

Migration

When data, workflows, or an interface have to move to another system or platform.

What we do

  • Data mapping, cleansing, and validation rules
  • Migration scripts with dry runs and reconciliation
  • Interface migration (file → API, on-prem → cloud)
  • Cut-over plan with go / no-go criteria

What you get

  • Reconciled data you can trust
  • A cut-over that was rehearsed, not improvised
  • Old and new running side by side until proven

Application domains

Applications for finance, operations, manufacturing, and service.

Most of what we build is a dashboard, an internal platform, or a workflow application that sits between people and the core systems — the place where the daily work actually happens.

Dashboards & reporting
Operational and management views on live data
Internal platforms
Planning, portfolio, request, and approval tools
Operator & mobile apps
Shop floor, field service, inspections, offline-capable
Portals & self-service
Customer, supplier, and employee facing
  • 01

    Finance

    • Approval and exception workflows
    • OCR + AI document intake
    • Savings and portfolio dashboards
  • 02

    Operations

    • Resource and machine planning
    • Request routing and follow-up
    • Product and fabrication finders
  • 03

    Manufacturing

    • MES-style execution support
    • Machine-connected operator apps
    • Traceability and batch records
  • 04

    Service

    • Installed-base monitoring
    • Inspection and maintenance flows
    • Assistant-style AI guidance

Integrations

Built to exchange data with SAP, Dynamics 365, ERP, CRM, and your APIs.

An application that does not talk to the core systems creates rekeying. We design the integration layer first: which system owns which data, how changes flow, and how failures are made visible.

  1. 01

    API integration

    REST / OData, authenticated, versioned, monitored

  2. 02

    Event & message based

    Queues and webhooks for near-real-time updates

  3. 03

    SAP IDoc / BAPI

    Documents and postings into ECC and S/4HANA

  4. 04

    Dynamics 365 Dataverse

    Finance, Supply Chain, Sales entities

  5. 05

    File & batch exchange

    Where it is still the pragmatic option — with reconciliation

Integration landscape

Reply Smart integration layer
Workflows · APIs · data contracts · monitoring
  • SAP

    S/4HANA · ECC

    • IDoc
    • OData
    • BAPI
  • Microsoft Dynamics 365

    Finance · SCM · Sales

    • OData
    • Dataverse
  • ERP

    Other ERP platforms

    • REST
    • File exchange
  • CRM

    Sales & service data

    • APIs
    • Events
  • IoT

    Sensors · PLCs · gateways

    • OPC UA
    • MQTT
  • Custom applications

    Portals · tools · APIs

    • REST
    • Webhooks

Examples

The kind of software we have built.

Described by pattern, not by name. Full cases with challenge, solution, and outcome are on the work page.

Go to the work page →
  • Internal platform · Operations

    Resource and machine planning platform

    Matching operators, skills, availability, and machine demand with rule-based support and controlled manual overrides.

    • Rules & solver logic
    • Web app
    • ERP data
  • Dashboard · Finance

    Application portfolio and savings dashboard

    Tracking applications, usage, investments, and realized versus projected savings without mixing forecasts with facts.

    • Dashboards
    • Governance
    • Data model
  • Rebuild · Operations

    Product and fabrication finder

    A searchable tool with data-quality checks and location visibility that replaced legacy request workflows.

    • Search
    • Legacy replacement
    • Data quality
  • New build · Engineering

    Engineering and calculation workflows

    Technical calculations, structured APIs, role-based access, and audit trails in a maintainable stack.

    • Calculations
    • APIs
    • Audit & access

Contact

Have an application that needs building, rebuilding, or moving?

We start with a short conversation about your situation and come back with a clear, honest view of what is worth automating, modernizing, or integrating first.

  1. 01

    A reply within two business days

  2. 02

    A focused discovery call, not a sales pitch

  3. 03

    A written proposal with scope, steps, and risks

  4. 04

    Direct contact with senior people from first call to go-live