<tools>how we work</tools>
Three pieces of software do a lot of our day-to-day work. One runs operations, one builds software with a person approving every step, and one audits sites for accessibility. We use them on our own work first. Some may become products.
Three tools
Projects, tasks, time and meetings in one place.
How it worksSoftware agents that plan and build. A person approves every plan and every merge.
How it worksWCAG 2.2 AA scans, reviewed by people and shared with clients as a private report.
How it worksOps Platform
Runs the studio dailyOps Platform is where we run VisualBoston. Projects, tasks, time and meeting notes live side by side, so nothing gets lost between apps. When a task is ready to build, it can go straight to Logan.
Logan
In pilotLogan writes a plan for a change, then waits. Once one of our engineers approves it, Logan builds it in a sandbox, runs the project's own checks, has a second agent check the work against the plan, and opens a pull request with before and after screenshots.
A11Y
Used on client auditsA11Y scans a whole site against WCAG 2.2 AA, groups what it finds so we can review it, and shares a private report with the client. Each new audit shows what changed since the last one. Automated scans catch about a third of issues, so we test by hand too.
How we build them
Logan writes the plan and the code. One of our engineers approves the plan before anything is built and reviews every pull request before it merges.
Every tool runs on VisualBoston projects before it touches anyone else's.
Scans catch about a third of accessibility issues. We test the rest by hand and with assistive technology.
Some of these may become products. Until then, they make the work we do for you faster and more careful. Tell us what you're building.