# One schedule, two systems in step.

> We kept the systems in step, so each lesson is entered once.

- Source: https://synconai.com/case-studies/education-scheduling-two-system-sync
- Publisher: SynconAI (https://synconai.com)
- Type: Case study
- Evidence: Delivered work
- Industry: Education
- Products: Salesforce Platform, Lightning Web Components, Apex, Flow
- Service: Salesforce Development (https://synconai.com/salesforce-development)
- Reading time: 1 minutes

## In short

We kept the systems in step, so each lesson is entered once.

## How we help

We kept the systems in step, so each lesson is entered once.

## Before and after

| Area | Before | After |
| --- | --- | --- |
| Scheduling | Entered twice | Entered once |
| View of the week | A list | A calendar |
| Systems | Disagreed | Stay in step |

## Results

- Less admin for coordinators
- Fewer scheduling mistakes
- Reports that match what happened

## How it works

Custom Salesforce development covers what configuration cannot: Apex for complex logic, Lightning Web Components for tailored interfaces, and integrations with the platforms a business already relies on.

Good custom code is maintainable code: tested, documented, and designed so your own team can own it after hand-over.

## Our approach

1. **Decide build or configure.** Use declarative tools first and write code only where it earns its place.
2. **Design.** Agree data ownership, interfaces and error handling before writing code.
3. **Build with tests.** Develop with meaningful tests and code review.
4. **Deploy safely.** Move through sandbox, user acceptance testing and production with source control.
5. **Hand over.** Document and walk your team through what was built.

## What to get right

- Give every piece of data one owning system.
- Make failures visible to an administrator.
- Keep business rules configurable, not hard-coded.
- Test with real scenarios before users rely on it.

## Questions

### When should we use custom code instead of Flow?

When logic is complex, performance matters, or an interface needs more than standard components. Otherwise Flow is easier to maintain.

### Can you integrate Salesforce with niche industry tools?

Yes. We build two-way integrations over the tool’s API with clear ownership of each field and visible error handling.

### Will our team be able to maintain it?

Yes. We document the build, keep rules configurable and walk your team through it at hand-over.

---

SynconAI. https://synconai.com/case-studies/education-scheduling-two-system-sync