# LinkedIn Service Page Fit

This page keeps my LinkedIn Services surface aligned with the work I actually want:
remote AI automation, backend/platform systems, CRM/ERP/API integration, internal tools, and
DevOps/recovery work.

The target routing surface is backend/platform, AI workflow, integration, data, and DevOps work.

Current LinkedIn Services categories observed on 2026-06-27:

- Cloud Application Development
- Web Development
- Application Development
- Custom Software Development
- Information Management
- IT Consulting

Read-only category picker observed on 2026-06-27:

- current six services leave four open slots before the 10-service limit;
- after removing `Web Development` and `Application Development`, the practical saved set can keep
  four current services and add six stronger services;
- available target services include `Cloud Management`, `Database Development`, `Business
  Analytics`, `Software Testing`, `Cybersecurity`, `Data Reporting`, and `Technical Support`;
- `Technical Support` is a fallback, not the primary add, because it can route generic support
  requests instead of backend/platform ownership.

Current live service-page assets observed on 2026-06-27:

- description: targeted to remote AI automation/backend systems, RAG/document pipelines,
  transcript/call analysis, Telegram approval, CRM/ERP/1C/bank API adapters, FastAPI/PostgreSQL,
  Docker/CI, logs, tests, runbooks, and recovery paths;
- availability: available;
- work mode: remote;
- pricing: contact for pricing;
- media: DriveDesk AI Operator proof route and AI Ops Workflow Kit proof route;
- broad-category routing can attract website refresh, standalone game, and generic
  mobile/ecommerce requests, which are not the target unless they include real backend/integration
  ownership.

The current description is already strong and targeted:

> I build remote-only AI automation/backend systems for real business workflows: RAG/document
> pipelines, transcript/call analysis, Telegram approval, CRM/ERP/1C/bank API adapters,
> FastAPI/PostgreSQL admin tools, Docker/CI, logs, tests, runbooks, and recovery paths. Send one
> messy workflow, one success condition, and the systems involved; I will propose the smallest
> working slice, proof route, and handoff path.

## Category Strategy

LinkedIn categories are broad routing labels, not the actual offer. The service page is triaged by
system ownership: backend/platform, AI workflow, integration, DevOps, data, internal operations, and
handoff quality. Categories that mostly route isolated websites, student assignments, standalone
games, or generic mobile/ecommerce requests should be removed or treated as not a fit.

Keep:

- Cloud Application Development
- Custom Software Development
- Information Management
- IT Consulting

Remove:

- Web Development
- Application Development

Primary add set:

- Cloud Management
- Database Development
- Data Reporting
- Business Analytics
- Software Testing
- Cybersecurity

Fallback only if one primary category is unavailable:

- Technical Support

Do not add:

- Mobile Application Development
- broad web-only categories
- categories that mainly route design, content, marketing, simple site refreshes, student work, or
  generic low-level support

## Request Triage Rule

Good fit:

- backend-owned AI workflow, RAG, transcript/call/document analysis, approval flow, CRM action, or
  internal operator workflow;
- CRM/ERP/1C/banking/accounting/API/database integration with contracts, retries, logs, and
  rollout notes;
- FastAPI/PostgreSQL backend, admin workflow, audit trail, worker/outbox, tests, Docker, CI, and
  runbook;
- DevOps/recovery/hardening work with deploy, logs, health checks, smoke tests, backup/restore, or
  rollback.

Not a fit unless there is a real backend/integration system to own:

- isolated website refresh;
- student or course assignment;
- standalone game clone;
- generic mobile/ecommerce app;
- vague request with no system boundary and no verifiable success condition.

## Exact LinkedIn Category Package

The next live category edit should use this package:

- remove `Web Development`;
- remove `Application Development`;
- keep `Cloud Application Development`;
- keep `Custom Software Development`;
- keep `Information Management`;
- keep `IT Consulting`;
- add `Cloud Management`;
- add `Database Development`;
- add `Business Analytics`;
- add `Software Testing`;
- add `Cybersecurity`;
- add `Data Reporting`.

Target saved package: 10 services total, with the two broad request magnets removed and six
backend/platform/data/security services added. Use `Technical Support` only as a fallback if one of
the primary add services cannot be selected.

Do not save a category set that removes the backend/platform/integration routing surface completely.
If broad requests continue to route generic mobile/ecommerce work without backend or integration
ownership, test a narrower category set and keep the public service page anchored to proof routes.

## Proof Route

- [Remote AI Automation Services](./SERVICES.md)
- [DriveDesk AI Operator proof route](https://alexgerlitz.github.io/AlexGerlitz/drivedesk-proof-route.html)
- [Fixed-scope offers](./FIXED_SCOPE_OFFERS.md)
- [Start conversation](https://alexgerlitz.github.io/AlexGerlitz/start-conversation.html)
- [Skill evidence](./SKILL_EVIDENCE.md)