Work

Small tools. Larger applications. Working websites.

The named organizations and records are fictional. The paired Talty websites are our own. You can judge every example by what it lets you do.

Custom application / fictional setting

Kettle Brook

One request, from the person asking for help to the staff doing the work.

Kettle Brook is a case-management application built around a fictional community-service organization. It gives participants a place to submit requests and see their progress, caseworkers a place to handle the work, and supervisors a way to assign it.

Staff view of a fictional utility-letter request, showing the assigned caseworker, participant details, reassignment, and status controls.
The staff view: a request in progress, its assigned caseworker, and controls for moving the work forward. Select the image to enlarge it.
See the same request from the participant's side
Participant view of the same fictional request, with its status, document upload, and conversation links, without staff notes or assignment controls.
The participant follows the request and supplies information. Staff-only notes, assignments, and history do not appear in this view.

Who uses it?

The participant
Creates a request, provides documents, answers follow-up questions, and checks the status.
The caseworker
Reviews the request and its files, keeps notes, and follows the tasks attached to the case.
The supervisor
Assigns cases to staff and reviews the team's work.

What makes this a larger build?

The application keeps records in a database and controls who can see or change them. Uploaded files go through a processing queue. Tasks, assignments, and case history remain attached to the request, so the next person can see what has happened.

The example uses community-service work, but the underlying needs are familiar elsewhere: applications to review, jobs to assign, documents to check, and people who need an update.

This is a demonstration build using fictional people and records, not a client installation. The full application's public, self-service demo is not available here. The smaller Records Desk below is a separate browser-only example.

Try the smaller document example · Discuss an application

Field service / fictional

Sixteen Below Mechanical

This field-service demo checks the service area, offers appointments based on crew capacity, prices the sample job, matches the work to a technician, and sends it to dispatch.

Open Sixteen Below Mechanical

Submissions + review / fictional

Penstock Review

Penstock is a fictional literary quarterly with an editorial intake desk. Submit a sample file, try blind review, score it with two readers, record a decision, withdraw it, and watch the queues change.

Open Penstock Review

The publication and everything in its sample records are fictional. Reset the demo whenever you want.

Readers + programs / owned

Talty Literary

Talty Literary has separate pages for classes, manuscript guidance, readings, readers, teachers, and organizations. Visitors can follow their interest from the homepage to the program details and relevant contact route.

Visit Talty Literary

Rights + records / fictional

Agency Rights Desk

Open one fictional client file and ask whether a right appears available. The desk keeps language, territory, format, exclusivity, and term separate, points back to the source record, and shows conflicts that need a person.

Open Agency Rights Desk

This is a routing and records demo. It does not grant rights or interpret a contract.

Browser-only document example / fictional

Kettle Brook Records Desk

Give the desk a sample letter. It reads the file in your browser, pulls out dates, amounts, references, and nearby deadline language, shows the rule it used, and sends the sample record to a staff queue.

Open Kettle Brook Records Desk

This is the earlier, smaller Kettle Brook example, not the full case-management application described above. The organization and records are fictional and resettable. Extracted text still needs human review.

Websites / owned

The paired Talty public sites

Talty Literary Solutions, Inc. runs two websites from one maintained source. Each has its own audience, navigation, voice, and policies. The release underneath them can be tested and rolled back.

What you can see

Two separate public experiences, shared code where it helps, and a tested release and rollback record.

The limit

This is TLS's own work. It is not a client result, accessibility certification, or guarantee of legal compliance.

What these examples mean

They show how TLS thinks and builds. They are not client testimonials, measured outcomes, certifications, or proof that the same design belongs in every organization.