Writing up recent work
Your project could be one of them.
Start one →
Shrimp Technology builds AI products, web apps and backend systems. We started out writing checkout and acquisition software, where a few milliseconds decide who gets the order, and we've built everything since with the same attention to speed.
Most of our work falls into six areas.
Assistants, agents and document workflows built on top of your own data, then measured against real tasks before they ship. We'll also tell you when a plain old script would do the job better.
This is where we started: checkout and acquisition software for limited releases, built to be first in line. Today we use that background for high-concurrency services, real-time pipelines and anything where latency costs you money.
Web and mobile apps, from a rough idea to something customers pay for. We handle design handoff, frontend, backend and deployment, and keep it running after launch.
APIs, databases, background jobs and the cloud setup underneath them. Sensible defaults, good monitoring and documentation someone else can actually follow.
Connecting the tools you already pay for, and replacing the spreadsheets and copy-pasting that sit between them.
Architecture reviews, code audits and a straight answer on whether that rewrite is worth it. Useful before you hire, raise or commit to a big build.
Proven tools, chosen for the job, not the trend.
- Languages
- TypeScriptRustGoPythonSwift
- Frontend
- ReactNext.jsReact NativeSwiftUI
- Backend & data
- Node & BunPostgreSQLRedisReal-time streams
- Performance
- Low-latency networkingHigh-concurrency servicesCheckout automationProfiling
- Infrastructure
- AWSCloudflareDockerCI/CD
- AI
- OpenAI & Anthropic APIsRAG & vector searchAgents & tool useEvals
- Also
- Developer toolingPayments
How a project usually goes.
A short call
Half an hour to understand the problem. If we're not the right fit, we'll tell you.
A written plan
Scope, timeline and cost on a page or two, agreed before anything gets built.
Weekly builds
A working version every week, plus a short note on what changed and what's next.
Case studies are on the way.
Tell us what you're building.
A few lines about the project is plenty to start. Rough is fine.