Artificial Intelligence
Artificial Intelligence That Earns Its Place
Search, recommendations, classification and assistants, built into the product rather than bolted onto it. Aliensync uses AI where it measurably improves something, and says so when it would not.
Honest starting point
Most AI features should not be built
That is an unusual thing for a software practice to say, so here is the reasoning.
An AI feature carries real ongoing cost: inference bills, latency, monitoring, and the awkward fact that it will sometimes be confidently wrong in front of a customer. That cost is worth paying when the feature replaces work a person is doing by hand, or makes something possible that was not. It is not worth paying so a product page can say the word.
So the first conversation is always about whether a simpler mechanism would do the job. Quite often a well-built search index, a sensible rule or a better form beats a model, and costs nothing to run.
Capabilities
Where AI genuinely pays
Semantic search
Finding the right thing when the user does not know the exact words for it.
- Vector search over your own content
- Hybrid keyword and meaning matching
- Synonym and typo tolerance
- Results you can explain
Recommendations and ranking
Deciding what each person sees first, which is most of what makes a social product feel good.
- Feed and content ranking
- Related items
- Personalisation with sensible defaults
- Cold-start handling
Classification and moderation
Sorting and screening at a volume no team could read.
- Content categorisation
- Spam and abuse detection
- Sentiment and intent tagging
- Human review queues for edge cases
Grounded assistants
Answering from your documents and data, not from the open internet.
- Retrieval over your own sources
- Citations back to the source
- Guardrails and refusals
- Logging for review
Method
How we keep AI features honest
- Define success before building. A number you can check, not a feeling that it seems better.
- Ground answers in your data. Retrieval first, generation second, with citations the user can follow.
- Design for being wrong. Confidence thresholds, fallbacks and a visible way for a person to correct it.
- Keep a human in the loop wherever the cost of an error is higher than the cost of a review.
- Log everything. Inputs, outputs and cost, so the feature can be audited and tuned instead of trusted blindly.
- Measure the bill. Inference cost per request, tracked from day one.

Data
What happens to your data
This is the question most clients care about most, so it should be answered plainly rather than buried.
| Question | Our default |
|---|---|
| Where does data live? | In infrastructure you own, in a region you choose |
| Is it used for training? | No. Providers are configured with training disabled |
| Who can see it? | Only the people you grant access to, with access logged |
| What is retained? | What you decide, with a retention policy set before launch |
| Can you change provider later? | Yes. We keep the model layer behind an interface for exactly that reason |
If an AI vendor cannot answer these five questions in writing, that is your answer about the vendor.
Questions
AI questions
Do we need our own model?
Almost certainly not. Training a model from scratch is expensive and rarely the bottleneck. Most useful AI features are retrieval and good prompting over an existing model, with your data doing the differentiating.
How accurate will it be?
That depends on the task, and anyone who gives you a percentage before seeing your data is making it up. What we do is agree how accuracy will be measured, build an evaluation set from your real examples, and report against it.
What does it cost to run?
Per-request inference cost is measurable and we track it from the first prototype, so the running cost is known before launch rather than discovered on the first invoice.
Can AI be added to software we already have?
Usually yes, and that is the most common request. It does not require rebuilding the product.
What if the model gives a wrong answer to a customer?
Design for it. Confidence thresholds, a fallback path, clear labelling of generated content and an easy route to a human. A feature without those is not finished.
Next step
Have a use case in mind?
Tell us the task you want handled and we will say whether AI is the right tool, what it would take, and what it would cost to run each month.
