Integrations that drop records, fail quietly or break when something changes

When orders, invoices or customer records move between systems and the first sign of trouble is a customer, or a month-end report that does not add up, the integration is the problem. I find out why, then fix it at a fixed price.

Want to talk it through? book a free 20-minute call or describe the problem.

What usually breaks

• Records go missing between systems. Sounds like: an order, invoice or contact feed that drops records without raising an error.
• Failures nobody hears about. Sounds like: a nightly job or sync that stops working and still reports success.
• It breaks when something else changes. Sounds like: a supplier updates their API, or a password, token or permission expires.
• It falls over when it is busy. Sounds like: timeouts at peak, or retries that create duplicates.
• Nobody can say what talks to what. Sounds like: the only map of the integrations is in one person's head.

What I do about it

First, find out what is actually wrong

For one known failure, the free 20-minute call is usually enough to quote a fix, or a fixed-price investigation if the cause is not yet clear. When you need the whole picture, the Integration Review maps up to five integration points and gives you a written picture of what would break first under change, with the fragile points that matter most in priority order.

Then fix or build it at a fixed price

The work is scoped in writing and quoted as a fixed price before it starts. Depending on what the integration needs, that can include:

• Validation of the data on the way in, so a bad record is caught rather than passed on
• Retries that cannot create duplicates, and a clear record of what was sent and when
• Monitoring and alerting that notices when nothing arrives, not only when something errors
• Microsoft Graph permissions set to what the integration actually needs
• Documentation of the endpoints and data mappings, so the integration no longer lives in one person's head

Fixed-price delivery carries a 30-day defect warranty from sign-off, and once the work is paid for in full, the code written specifically for you is yours.

What I build integrations with

• C# and .NET
• Azure Functions
• Azure Service Bus
• Azure SQL and SQL Server
• Azure Storage
• Microsoft Graph
• REST APIs
• Entity Framework
• FreeAgent API
• HubSpot API
• Google APIs
• LinkedIn API

Where sensitive information is involved, data handling can align with Microsoft Information Protection requirements. I work inside your access model: see working with your IT team.

Integrations I run myself

These are PageTech's own systems, written up with what went wrong as well as what worked:

• Real-time calendar integration: Outlook availability published through Microsoft Graph for the booking flow to read.
• Google APIs integration suite: GA4, Google Ads, Search Console and Bing data pulled into first-party SQL on a schedule.
• Fifteen API routes that never existed: an accounting proxy with 170 routes, fifteen of which pointed at endpoints that do not exist.
• Six weeks of ‘done’ that did nothing: a daily sync that logged success while a missing permission refused every read.

Who this is for

Businesses of any size whose day-to-day work depends on data moving between systems: a finance package, a CRM, a shared mailbox, a database, a supplier's API. You do not need to know which part is at fault before getting in touch.

Explore related areas

Compare the fixed-price reviews · Workflow Engineering · Production Reliability · Maintainability

Discuss an integration problem

A short conversation is usually the best place to begin. Delivery is 100% remote. Prefer to see evidence first? See real project examples. Read what people I have worked with say.

Book a free 20-minute call Describe the problem See the Integration Review