Work
Software Ebenstone has built.
Two were built for others: a church’s care app and a writing group’s website. The other three are Ebenstone’s own products. Each started as an idea for fixing a real problem. Each case study tells what the problem was, why it was built, and how each part of the problem was solved.
Built for others
Built for a client
A church’s care team can see every request, who has it, and what happens next.
Built for Calvary Chapel Oceanside. In use 18 days after the first conversation.
Read the case study
A website Ebenstone built
A home for a writing group’s first book.
One page for ten young authors and their anthology: the book first, each author, and what comes next.
Read the case studyEbenstone’s own products
Ebenstone’s own product
Live football stats, scored from a sideline with no signal.
Record the play and every total works itself out. Families follow live on a free link.
Read the case study
Ebenstone’s own product
A one-year reading plan a whole household follows together.
Everyone on the same plan, a quiz that confirms the reading happened, and a way to catch up after a missed day.
Read the case study
Ebenstone’s own product
Online ordering for shops that make things to order.
Every product has its own lead time, so a customer sees only the days they can actually have it.
Read the case studyIn common
What all of them have in common
Many organizations on one system
Shops, teams and households each see only their own, on one application that is maintained once.
Each organization’s data kept separate
The boundaries are part of the database design from the first version. This is what a security questionnaire is asking about.
It works when the connection drops
A sideline, a parking lot, a basement. The software holds what was entered and sends it when the signal returns.
Have a problem like one of these?
Tell me what it is and what you use now.
or write to [email protected]