# Web development and integrations around your AI product

> Connect websites, CRM, booking, customer interfaces and approved business tools around an existing AI product, with tested handovers and clear ownership.

Canonical page: https://webvelopment.co.za/industry-solutions/ai-companies/integrations/

Language: en

AI companies · Web Development & Integrations

A website form, a booking tool, a CRM and a subscription platform can all work individually while the customer journey between them remains unreliable. Records arrive twice, ownership is unclear or important events are lost when a service is unavailable.

[Discuss your AI-company project](https://webvelopment.co.za/contact/)

Webvelopment scopes the interfaces and customer-facing infrastructure needed to connect that journey. Model behaviour, training and inference operations remain with the team responsible for the AI product.

## Start with the handover

![Application code displayed on a desktop monitor.](https://webvelopment.co.za/images/lifestyle/code-review-1400.webp)

Illustrative photography · [Karl Pawlowicz / Unsplash](https://unsplash.com/photos/a-computer-monitor-sitting-on-top-of-a-wooden-desk-QUHuwyNgSA0)

Before choosing a connector, define what should happen. Which event starts the process? What information is necessary? Which system owns the record? Who can change it? What should happen when the same event arrives twice, or when the receiving service is temporarily unavailable?

These questions turn a vague request to “integrate everything” into an implementable contract. The aim is not simply to move data, but to preserve its meaning and make failures visible.

## What can be scoped

### Website-to-CRM and booking integrations

Capture a business enquiry, validate the required fields, preserve approved campaign context and assign the next action. Make confirmation depend on a genuine accepted handover rather than a client-side animation.

### Customer-facing portals and dashboards

Build bounded interfaces around approved APIs and access rules. Define authentication, permissions, available data, error states and operational support separately from the visual design.

### Documentation experiences

Implement navigation, search, versioning, publishing and page templates around the client’s technical material. Engineers must validate API behaviour and runnable examples; a documentation interface does not confer authority over the product’s semantics.

### Product and commercial event connections

Connect approved account-level events to the systems that need them. A marketing or revenue report generally does not need the raw contents of a customer prompt or model response.

### Billing and business-tool interfaces

Integrate supported provider interfaces where merchant eligibility, financial rules and the client architecture permit it. Payment processing, entitlement decisions and accounting definitions require their own owners and testing.

## Reliability is part of the deliverable

A happy-path test is necessary but insufficient. The implementation should address duplicate delivery, invalid input, timeouts, retries, permission failures and reconciliation. Receiving a webhook is different from successfully applying its business effect.

For example, a confirmed payment event might arrive more than once or out of order. The integration needs a strategy for identifying the event, applying the appropriate state and avoiding duplicate effects. Provider-specific implementation should follow current official documentation; [Stripe’s webhook guidance](https://docs.stripe.com/webhooks) is one example of these operational concerns.

Monitoring also needs an owner. A system that records an error nobody reviews is not meaningfully monitored.

## Keep sensitive data out of the wrong systems

Define the minimum data each interface requires. Public forms should not collect API secrets, confidential prompts, customer datasets or documents unrelated to the enquiry. Analytics events should not become copies of CRM records.

Use approved access controls, secret management, logging and retention arrangements for the actual implementation. A business contact ID may still be sensitive in context; pseudonymous identifiers are not automatically harmless.

Legal and security requirements must be reviewed for the specific processing arrangement. We support technical controls and specialist collaboration rather than promising compliance certification.

## Website, application and backend responsibilities

A static marketing site can present information and submit to an approved backend. It should not contain private credentials or become the hidden owner of subscription logic. An authenticated application has different access and operational requirements.

We define those boundaries before implementation. A public calculator running locally in a browser is not the same project as a multi-user financial dashboard. A front-end prototype is not a production service until its backend, access and support requirements are satisfied.

## What a good handover includes

The agreed data model, field mapping, event contract, authentication approach, test evidence, monitoring, recovery procedure and ownership should be documented. Code and account ownership must follow the agreement and relevant third-party licences.

Your team should know what happens when a provider changes an API, a credential expires or a record cannot be reconciled. Ongoing maintenance and response expectations should be explicitly scoped.

## A worked example: the duplicate payment event

Payment providers retry webhooks. The same “payment succeeded” event can arrive twice, or after a newer “subscription cancelled” event. If the integration simply processes what arrives, a customer gets two entitlements, or a cancelled account is quietly reactivated. A reliable integration recognises the duplicate, reconciles against the authoritative state and never lets an older event overwrite a newer one. That’s the difference between an integration that demos well and one that survives production.

## How we test it

Before sign-off: a normal event has the intended effect; a duplicate doesn’t duplicate it; invalid signatures and unauthorised requests are rejected; retries are bounded and visible; out-of-order events can’t silently roll state back; sensitive fields stay out of logs and analytics; reconciliation finds missing records; and your team can recover a failed item using the runbook.

## Integrations we’ve built

We’ve connected systems to Salesforce, Zoho, Leadtrekker, Basecloud, Shopify, Sage, PayFast, TransUnion and the OpenAI API, alongside vehicle-stock and finance platforms such as AutoTrader, Evolve and WesBank. The [Digicars Group platform](https://webvelopment.co.za/work/digicars-group-platform/) runs 17 dealer websites from one connected system. None of that makes us a partner of any vendor, but it does mean we read API contracts carefully, keep secrets server-side and build monitoring that tells someone when a sync stops.

## Questions about integration projects

A few useful answers before you decide.

### Can you integrate with our existing software?

Possibly, depending on supported APIs, access, licensing, security requirements and the exact workflow. A discovery step should confirm those conditions before promising a specific connector or delivery date.

### Do we need a custom platform?

Not necessarily. Configuration or a smaller integration may solve the problem. Custom development is justified when a real requirement cannot be met more simply and the business can support the resulting system.

### Can you build the AI backend too?

That is outside this offering. We focus on public and customer-facing infrastructure and approved business integrations around an existing product.

### Is a successful API response enough to sign off?

No. Acceptance should confirm the intended business effect, duplicate and failure behaviour, reconciliation and operational ownership. A transport-level success alone can hide an incomplete workflow.

[Discuss a bounded integration project](https://webvelopment.co.za/contact/) · [Explore revenue operations](https://webvelopment.co.za/industry-solutions/ai-companies/revenue-operations/)

Keep exploring

## Keep the right things connected.

[AI companies · Data & Revenue Operations

### Commercial analytics and revenue operations for AI companies

Make the commercial numbers agree before asking them to guide growth.](https://webvelopment.co.za/industry-solutions/ai-companies/revenue-operations/)[AI companies · Websites & Product Marketing

### Website development for AI and SaaS companies

Build a product website that helps the right people understand what to do next.](https://webvelopment.co.za/industry-solutions/ai-companies/website-development/)[AI companies · Design & Creative

### Product design and creative for AI companies

Make the product understandable before making it impressive.](https://webvelopment.co.za/industry-solutions/ai-companies/product-design/)

Let’s move things forward

## Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

[Discuss your AI-company project](https://webvelopment.co.za/contact/)