The five items we tabled before launch, built right by the team that built the theme.
SCHR launched a month ago on a custom theme we built. A handful of features got tabled to hit the date. They're still on the list.
Your IT team can technically touch the site, but it's not their focus and the queue is long. Changes wait.
You'd rather email the people who built the theme and get it handled. That's us.
Working range, pre-kickoff. We bill T&M against actual hours every month. Discovery's job is to tighten the picture, not loosen it. The cleaner we get on scope, the tighter this gets. Final number locks before we ship.
Design and dev bundled. Overhead (PM, design review, QA) is on the scope spread.
A new component that overlays a caption on an image. Drop it into any page.
A mega menu that surfaces a featured event, image, button, or both. The one real lift in the list.
An edit surface for the events archive so your team can change the headline and intro text without a developer.
A new page that pulls events by date and houses post-event galleries, videos, and recaps. One link instead of an email.
Strip the Next and Previous arrows off the post nav. Small, but it's been bugging you.
The unlimited Advanced Custom Fields key we owe you, installed on the site.
Requests sit in a queue behind everything else. Each change risks breaking something nobody fully understands.
"There is a little bit of a time delay there."
We know the back end, the custom post types, and what the theme can do. You email, we handle it, nothing breaks.
"It's always nice to have access to the original theme developers."
"It would just be super helpful to send an email and just say: here's this thing. What do you think?"
You've got the scope, the timeline, and the number. Phase 1 is these six items, fixed price, about 2 weeks from kickoff. Give it a yes and I'll send the task list and paperwork so George can start.
Brian Hammond
VP of Sales, FYC Labs
bhammond@fyclabs.com
fyclabs.com