This is a quick note for our Táve 2 users: You probably noticed a large Táve 3.0 Early Access banner on the left side of the application. Clicking on the banner will take you to the 3.0 migration website, where you’ll be able to configure a preview migration or go live with the new version. Once the migration is complete, you’ll be able to sign-in to the new Táve 3.0 Early Access site at my.tave.com.

Thank you for your patience and support as we worked long and hard to develop Táve 3!

Táve 2.9 registration has been closed for the 3.0 rollout.

3.0 registration will begin on the afternoon of Tuesday, February 7th.

If you don’t have an existing account, please sign-up for our newsletter to receive an email when Táve 3.0 registration begins.

We’ve received several reports of studios who use GMail not seeing new lead emails due to GMail marking the email as Spam. While unconfirmed, it’s possibile that emails sent from studios via Táve to GMail recipients may be affected by this issue as well. This issue affects both Táve 2 and 3.

Our outgoing mail has been independently verified to pass all anti-spam checks, including SPF, DKIM, and SpamAssassin, so we believe this to be an isolated issue with GMail.

Workaround: While we work to resolve the issue, GMail users should add a rule in their GMail settings to never mark email coming from @tave.com as spam (and we suggest having it mark the message as important). Also, check your Táve daily for new leads as they will always show up there even if the email notice doesn’t reach you.

RESOLVED (1/25):Our outgoing email is now using new IP addresses and our test emails have been delivered successfully. Please comment or post a Helpdesk ticket if a new lead message goes to your spam or isn’t delivered after 2PM Eastern today (Wednesday, January 25th).

UPDATE (1/30): The issue appears to still exist for some studios, with some users now receiving the messages and others still having them marked as spam or undelivered. We continue to investigate and are working with our email service provider for a solution. Please see the workaround in the meantime.

The holidays brought with them some major Táve 3 developments!

Those of you following @TaveStudio on Twitter may have seen that we launched our first Táve 3 studio on Monday. Of course my lovely wife and extremely talented Karen Lisa was the first to make the jump. We look forward to many new Táve 3 tutorials from her soon!

Since Monday, we’ve launched 5 more studios. Once these studios report that they’re all set up and actively using the system without any show stoppers, we’ll start inviting the rest of our 75 beta studios to go live with 3.0 “Early Access” as well. Then, once those studios have upgraded and report the same success and we have the system better documented, we’ll begin sending invitations out to existing Táve 2 subscribers to preview or upgrade their accounts. After that calms down we’ll put together a new public website and open up direct registration to Táve 3.

We’re calling it “Early Access” and rolling it out in stages because there’s still some important work to be done (such as mobile access), testing to be done (we haven’t done much testing outside of Google’s Chrome browser), and the 3.0 documentation is very limited. But even so, Táve 3 has advanced to the point that we believe it’s the better version for most of our users, especially considering all the amazing new features! Since we’ve designed the upgrade system to be user controlled and provide a way to preview your account in Táve 3, it makes sense to provide access earlier than if we had to meet the needs of all of our users at once for a system-wide simultaneous upgrade.

How long until everybody is invited to upgrade? That depends on how well each one of the steps outlined above goes, so there’s no way to say for sure, but we’re striving to get it out as quickly as possible. We’ll keep our Twitter account and Facebook page updated with the latest progress, so follow them if you want the latest details as we go. When you’re invited, we’ll send an email to your studio’s email address listed in Táve 2. If you don’t have a Táve 2 account, sign up for our Táve 3 newsletter on our homepage so you’re emailed when general registration is opened.

I try to include previews in our blog posts, but in celebration of the 3.0 Early Access release, why not check out an actual live Táve 3 demo questionnaire I created using the default brand theme?

Have a happy new year!

Update: The migration was completed successfully.  We were down for maintenance for just over an hour, about one third of our scheduled window. If you encounter any issues, please file a helpdesk ticket.

We’ll be moving from our servers based in Dallas, Texas, to Amazon’s AWS cloud starting at 11pm EST (Click the link to view the time in major cities around the globe). This will be a 3-hour window, but we’re aiming to have the system back online within an hour.

This blog and files uploaded by users in Táve 2.9 are already in the AWS cloud and every piece of the Táve 3.0 beta has been in AWS from the start as well. Wednesday’s migration completes our transition by moving the remaining 2.9 infrastructure. We’d wait until after the 3.0 release, but having 2.9 on AWS before then will dramatically speed up the studio-initiated upgrade system and also makes it easier for us to maintain both systems, as they’ll now have similar infrastructure behind them.

If this migration announcement seems familiar, you may recall we had planned on migrating back in March but postponed it due to an issue with Amazon’s email services. That has been resolved and in fact the new email service provider means we can now send emails from your studio without listing Táve as the Sender in Táve 3.0.

With our final and largest beta being readied for release to our beta testers, today’s 3.0 preview post will be longer than usual as Beta 5 covers a lot of ground.

Beta 5 is all about the client facing items. Proposals, questionnaires, invoices, and contact forms are all added or recreated with this release. Client Access as it was in T2 is no more. With T3, clients access items directly, be it an invoice, a questionnaire, or a proposal. With this, Brands become much more important and far more powerful.

In T3, your public look and feel, your contact information, and even custom domains are all determined by the brand. As part of this, we’ve added more color and image settings, including separate email and printout graphics (as well as container HTML for emails and printouts in the advanced configuration page).

With these options you can easily create highly customized pages without ever touching the advanced configuration page. With the exception of the invoice screenshot that illustrates how customizable the design is, all of the screenshots below use the default options. If you don’t provide a page background, we add a texture to your background color to make the page a bit less plain.

We had to change the proposal editor inside the app (compared to the prior version) to handle the additional features. The advantage of the new layout is we can show more information on the page.

When you hover over the recipient, several icons appear, including one to email an invitation to the recipient and another to open the direct link in another window. Using the Email Proposal button at the top, all of the recipients will be sent their own trackable direct link in an email you compose. Unlike T2, there isn’t a preview mode as that often caused confusion for users, instead we added a button to resets the statistics for the proposal. Clicking on the direct link icon pulls up the proposal either on your brand’s custom domain or its secure tave.com subdomain.

In this example proposal, I’ve provided two quotes, which are displayed along with my introduction (the order is customizable too, another new feature in T3). You’ll notice that the links showing the steps to book the proposal are now textual, allowing your brand to completely customize the look of them, a welcome change from T2 with its hard-coded Client Access navigation design. The orange colors in this Brand come from the default accent color seen in the first screenshot above.

The contact information below the page is all configured on the Brand as well. The screenshot above highlights two completely fictional quotes, one using a package and the other not. There’s an option to show individual package item prices as well as the package discount, but it isn’t enabled in this screenshot. Another new feature here is the ability for your client to explicitly decline a quote, which may provide more insight into what your client’s are looking for. The final item in the second quote, “Wedding Art Prints”, is followed by a description from the new product editor.

In the next screenshot, the client has selected the Gold Collection above and is prompted to select the payment schedule that works best for them. If you only added one payment schedule to the proposal they skip this step and continue on.

The subsequent pages are exactly what you’d expect, so I’ll skip them here, but the configuration for two of the steps are worth highlighting. Contracts have been improved with more explicit “initial here” boxes, many more placeholders, a copy of the sales order, and 1-4 signers (T2 was only 1 or 2, and it could only be set on the contract itself). Here’s a small clip from the Proposal’s contract editor, where you can configure those signatures and preview the quote based on which quote and payment schedule are selected.

The payment system in T3 has been enhanced to add an “Offline Cash Payments” option and you can now enable multiple payment options, so your client can select to mail you a check, pay with PayPal or Google Checkout, or use a credit card with your merchant account.

To illustrate just how customizable the new client facing pages are, here’s an invoice page using Karen’s brand design. When you or your workflow email an invoice to a client, they receive a direct link to this page.

There you have it, the highlights from the final Táve 3.0 beta!

Táve 3.0 Release Plan

With only a few small exceptions, like simplifying the new New Lead Wizard, this beta essentially brings us to feature complete status. That’s quite a milestone when you consider my very first code submission labeled as 3.0 was on November 2nd, 2009 (changelist 3009 and we’re on change 5960 now, though we did release 2.8 and 2.9 between then and now it still illustrates how nearly as many changes have gone into 3.0 as have gone into all prior releases combined).

We’ll be working out the details and scheduling of the public release over the next couple weeks and will post more details about that then.

When we began work on Beta 5, our final beta, in early August, we were aiming for a 2 month release schedule. It appears we’ll be pretty close to that goal as we’re now down to 10 points for this iteration in our project plan (our points are averaging about one day). Beta 5 is extremely exciting, as it completely replaces our client facing pages from T2, bringing far more attractive default designs, superior browser compatibility, and many more features. We’ll go deeper into it in our Beta 5 preview in two weeks.

In the meantime, I’d like to illustrate how some of the fairly simple changes in T3 can have a huge impact on what you get out of the system, by sharing a preview of the new sidebars from the Jobs and Contacts homepages. The Job section opens with an overview highlighting revenue (including a small chart), jobs that need attention, upcoming payments, etc. The Contacts section however, which replaces the Clients and Vendors sections, is more of an address book and thus opens directly to your full contact list.

One of the things we’ve been hearing about in T2 is that it isn’t always easy to get to your open leads or booked jobs, check account balances, or export only certain items. With the new lists in T3, all of that and more is available with a quick click (filtering is no longer required). We’ve also added a few other useful features here, like being able to star jobs and contacts that you want to quickly access later, to allowing bulk changes to the items (such as deleting or completing multiple items at once).

We’ve mentioned in earlier posts how contacts in T3 can be re-used around the app, being a client here, a subject there, and a vendor on another job. These lists bring all that together. For instance, adding a contact as a vendor on a job automatically adds them to the vendors list, rather than having a separate Vendors section as we do in T2.

Speaking of organizing important items, we also replaced the “Attention Needed” box on the homepage, which had a tendency to get rather massive for busy studios by listing each item right there, with a new “Right Now” summarized snapshot of your studio that links various item counts to these new lists.

These screenshots were taken with my test studio, so your actual data will make more sense than mine.

In Closing

We’ve had mixed reaction to our preview posts, with some feeling reassured that we’re doing the right thing and on track but others feeling teased by them. So we’ve spent the last couple months (as we in hurricane country say) ”hunkered down” focused on development of this final beta, knowing that what everybody really wants (us included!) is the final T3 release announcement. Once Beta 5 completes the beta process, we intend to ramp up our communication significantly.

Until then, and as always, we’re available via Helpdesk. Thank you for your support!

In our previous Táve 3.0 preview series post, we looked at the new workflow system. Moving the workflow into its own section meant we could clean up and simplify the product editor, which had always been a bit of a challenge for new users to really jump into. Now all the work to create when ordered and default expenses are completely separate from the product editor. This also means you can reuse the same product workflow for multiple products, saving even more time.

Options and add-ons can be added and edited directly on the product page now, and add-on pricing is now located in the add-on quick editor instead of being grouped with all the other product pricing configuration. These popup quick editors are also new to Beta 4, replacing the inline quick editors used throughout the application due to feedback from previous betas.

When it comes to editing the pricing of complex products, such as albums, it’s easier and clearer than ever. We’ve also optimized it to handle larger and more complex products much more efficiently than before.

Jason and I are excited about today’s substantial Beta 4 release for many reasons. One significant update includes a major upgrade to our javascript framework that speeds up initial load so much that we’ve removed the loading screen. Another reason I’m personally excited about Beta 4 is that it means my focus now moves to the client-facing products, which are the last major components to deliver before we hit feature-complete status across all products and start planning the Early Access release schedule.

Táve has always had a versatile product-based workflow, and with Táve 3.0 Beta 4 we’re taking that to a whole new level.

First, we’ve moved the workflow from the product editor into its own editor. This has the advantage of letting you re-use and manage the same workflow across multiple products much easier than before.

Then we expanded the existing list of items that you could create from just tasks, events, and expenses. Now you can have credit automatically added or redeemed during any phase. In addition this powers our most frequently requested feature; you can have the system create and (optionally) automatically send emails to your clients using the new Quick Response feature.

To make the workflow even more powerful, we’ve expanded it to include job-based workflow. Now you can have items that get created the moment a lead comes in or applied to any job regardless of what products they’ve booked.

Because the workflow system is completely customizable, this also means you can now modify the phases in a job or deliverable, adding or removing them as you wish.

In this screenshot (click to view full size), I’ve created a very basic job workflow illustrating some of the things that can be done in Táve 3.0. A few of the items would be more appropriate on a deliverable workflow, but they illustrate the potential.

PS. Have you seen the photos of our new office we posted to Facebook? We’ve been putting the new office to good use with lots of 3.0 development and continuing the rapid helpdesk response times we’re known for.

While we’re not ready to give an estimate on when 3.0 will be released, I’d like to shed some light where Táve 3.0 stands right now.

The New Release Plan

The last time we discussed how the 3.0 release was going to work, it was essentially the same as any other release in that all studios would receive the update the moment we published it. All studios would be on 2.9 one day, and then using 3.0 the next.

The feedback we’ve been hearing from our beta testers has generally been that 3.0 is absolutely amazing, but also such a large change that they’d really prefer to upgrade on their own schedule.

So we’re doing two things. First, we’re going to be opening up a Preview Release to all subscribers, so you have a chance to dive into it and get familiar with 3.0, complete with your 2.9 data.

In addition, since we have a worldwide userbase, the 3.0 release will inevitably end up being in some users’ busy season and some users enjoy being early adopters while others prefer to wait for an update or two to be released, we’re switching to an opt-in upgrade that will give studios plenty of time to make the jump. It also means we’ll be able to let those more adventurous users or those who are only looking for a particular feature, to start using 3.0 even earlier than we had planned.

The Roadmap

We recently switched to a new agile development process, called scrum, and with that change firmed up our roadmap. Once we get through another iteration or two we should have enough data to confidently discuss timelines, but until then let’s look at the release plan at a higher level.

If you’ve been following the blog you’ll know we recently released Beta 3 to our private beta community, and as I mentioned in my last blog post, Beta 4 will introduce a new workflow system and section (it also replaces the oldest piece of our application, the Products section). With Beta 4, the manager will essentially be at “feature complete” status. With Beta 5, the final beta, all the client-facing systems will also reach “feature complete” status and we’ll switch to primarily fixing bugs and addressing issues found by our beta testers.

The next release after B5 will be quite exciting; the Táve 3.0 Preview Release! The preview will allow all of our subscribers to preview 3.0 using their current data. As mentioned above, it’ll let you get familiar with 3.0 so you’re ready for its release. It’ll also let you help find any bugs or issues that could hamper your use of 3.0.

It keeps getting more exciting with each release, because the PR will be followed by Táve 3.0 Early Access, and as the name implies, existing users will be able to upgrade their accounts to use 3.0 at this point, prior to the final release (and new users will be able to create Early Access accounts directly without first setting up 2.9, though they’ll still be able to if they wish). For many, this will be no different than a 3.0 release.

The Early Access release will be followed by the final Táve 3.0 release: General Availability, the actual release with all the new documentation and videos, the new public website, and end of 2.9 registration. To those who upgraded during the Early Access release, this will seem more like a 3.1 release.

As I mentioned in the release plan section above, 2.9 users will be able to continue using 2.9 even after GA and will have until the end of the year to self-upgrade.

P.S. We Love You

It’s been a long journey and the road has a few more stops ahead, but only a few now. We may not post updates each step of the way, but we are getting there and I sincerely appreciate your desire to use 3.0 ASAP and I thank you for your patience and continued support as we work toward its release.