The software your business runs on, in a browser.
Customer portals, operational dashboards, booking systems, internal tools. The things a spreadsheet used to do until it stopped coping. Scoped in a week, built in three, live in four.
- 4 weeks
- scope to live
- Fixed price
- against a written scope
- Week 2
- first working demo
Who this is for
You probably need this if…
01
A spreadsheet is running something important
It started as a quick tracker and now three people depend on it, it breaks when two of them edit at once, and nobody is sure which copy is current.
02
Your systems don't talk to each other
Data gets re-keyed between tools every day. Someone's evening job is copying numbers from one screen into another, and the numbers still disagree.
03
Off-the-shelf nearly fits
You've tried the SaaS products. Each does eighty per cent and forces you to change how you work for the other twenty. The twenty is the part that makes you money.
What we build
The work, in detail.
Portals & dashboards
Customer-facing portals and internal operational views. Role-scoped, so each person sees exactly what they should and nothing they shouldn't.
Real-time features
Live updates, collaborative editing, presence, instant notifications. Built on WebSockets and server-sent events rather than polling every few seconds.
API & integration layers
REST and GraphQL APIs, webhook handling, and the orchestration that makes several third-party services behave as one coherent system.
Auth, roles & audit
Authentication, granular permissions, SSO where you need it, and audit logging so you can answer who changed what, and when.
Performance & scale
Server-side rendering, sensible caching, query optimisation and background job processing. Fast on day one and still fast at ten times the data.
Responsive & offline
Works properly on a phone in a stockroom, not just on a desk. Progressive web apps where installability and offline access genuinely matter.
AI where it earns its place
Search that understands intent, document extraction, assistants grounded in your own data. Added because it removes work, not because it demos well.
Multi-tenancy
One system, many organisations, clean separation between them. Already solved on the Sill platform rather than invented for your project.
Practice areas
The disciplines behind it.
You buy this as one engagement at one price. Underneath, it draws on 4 of our practice areas, and the same people cover all of them.
Product Engineering
The core build. Web and mobile applications from scoped spec to production.
- Web applications
- iOS & Android
- API design
- Real-time features
Design & Experience
Interfaces people can use without being trained on them.
- Product UI design
- Interaction design
- Design systems
- Prototyping
Quality & Testing
Knowing it works before a customer tells you that it does not.
- Automated test suites
- End-to-end testing
- Load & stress testing
- Accessibility testing
Security & Access
Who can see what, proven rather than assumed.
- Authentication
- Roles & permissions
- Tenant isolation
- Audit logging
How it runs
Four weeks, in order.
Week 1
Scope
Access to your systems, a walkthrough of how the work happens today, and a written specification you sign off. No code until you've agreed what it is.
Week 2
Build
Core data model, authentication, and the primary workflow. Friday demo on your real data — something you can click, not a progress bar.
Week 3
Build
Reporting, permissions, integrations and the edge cases that only surface once you've used it. Second Friday demo.
Week 4
Ship
Deployment, monitoring, migration of existing data, training for your team, and documentation written for people rather than engineers.
What you get, concretely
- A live, deployed application on your infrastructure or ours
- Source code in a repository you own from the first commit
- Written technical specification, signed off before build
- Admin interface so you can manage it without calling us
- Two training sessions with your team, recorded
- Plain-language documentation, not auto-generated API dumps
- 30 days of post-launch fixes at no additional cost
Typical engagement
Fixed price · four weeks
What moves the number is how many integrations are involved and whether existing data needs migrating. Quoted against a written spec, and it does not move after you sign.
Technology
What we build it with.
Defaults, not requirements. If you already run something else and have a team who knows it, we work in yours.
- Frontend
- React, Next.js, TypeScript, Tailwind CSS
- Backend
- Node.js, NestJS, REST & GraphQL, Prisma
- Data
- PostgreSQL, Redis, BullMQ job queues
- Infrastructure
- AWS, Vercel, Docker, CI/CD pipelines
Proof
We have built this before.
Not a reference we cannot name. Systems we designed, shipped and still operate, with the decisions written down.
Personal finance
Charten
Know exactly what you're worth.
Restaurants
InvtoryX
Back-of-house for restaurant groups that have more than one house.
Household
Larder
A kitchen that knows what is actually in it.
Restaurants & retail
Eshop
A storefront that agrees with the till.
Delivery platform
Sill
The layer every engagement starts on.
Questions
What people ask before signing.
- What if my project is bigger than four weeks?
- Some genuinely are. We'll say so on the first call and quote what it actually is, usually as two phases with something useful live at the end of the first. What we won't do is quote four weeks and discover the truth in month two.
- Do I own the code?
- Yes, and from the first commit rather than at handover. The repository is created under your account with us as collaborators. If you walk away mid-project, you keep everything built so far.
- Can you work with our existing system?
- Usually. We spend week one understanding what's there. Sometimes the honest answer is that a rebuild costs less than the integration — if that's the case we'll show you the arithmetic rather than just asserting it.
- What happens after launch?
- Thirty days of fixes are included. After that most clients move to a monthly support retainer, but there is no obligation — plenty of people take the code and run it themselves.
- Who actually builds it?
- The engineer who scoped it on your first call. No handoff to a different team, no junior inheriting the project in week three.
- What do you need from us?
- About three hours a week: a Friday demo and a handful of decisions. Plus system access and one named person who can answer questions without convening a committee.
Related reading
Written on this, by us.
How We Work · 8 min read
What Actually Goes in a Software Specification
A specification you can quote against is not a wish list. Here is what a useful one contains, what it deliberately leaves out, and how to tell a weak one.
Data & Integration · 7 min read
Multi-Location Is a Permissions Problem Wearing an Inventory Costume
Adding multi-site support with a location column works until one person holds different authority at two sites. Then it quietly leaks data.
Data & Integration · 6 min read
Idempotency: The One Word That Stops You Charging Someone Twice
The most common serious bug in payment code is not fraud or a failed gateway. It is a retry that creates a second charge, and it is entirely preventable.
Tell us what your spreadsheet is doing.
Describe the process that's outgrown its current tool. We'll come back within one business day with a scope, a number and a date.
Phone
+1 (407) 796-2376Reply time
One business day, from an engineer
Based in
Orlando, Florida · serving the United States
What happens next
- A reply within one business day, from an engineer
- A thirty-minute call, with no qualifying call before it
- A written scope and a fixed number, if it fits